Back to the developer overview

Planning your integration

Plan clearly.
Start step by step.

A clear first use case keeps your integration manageable. Start with one complete workflow and expand it deliberately.

A practical example

You want to display bookings from connected platforms in your software. Start with a small agreed set of properties and one platform: from an incoming booking to its correct display in your application. Add further workflows afterwards.

Start with a concrete goal

First describe what your users should be able to do. Which data is needed, which events trigger the workflow, and how will you recognise a correct result? A clear workflow is more useful than a long list of possible endpoints.

Agree on the initial scope

Agree with us on the functions, properties and platforms needed to get started. Also clarify access, activation and suitable test cases. Keep the pilot deliberately small, but cover the chosen workflow end to end.

Verify first, then expand

Alongside the normal case, check delayed changes, duplicate events and interruptions. Decide who detects errors and how missing data is reconciled. Once the workflow operates reliably and transparently, add more properties, platforms or functions.

Frequently asked questions

What can I connect through the feondi REST API?

You can connect a PMS, a custom application or a website to feondi. The API documentation describes resources for properties, media, rates, availability, bookings and webhook subscriptions.

How do I start an API integration?

Start with the REST API documentation and tell us about your use case. Together we will agree on access, data mapping, required platforms and activation.

Which plan applies to a direct API connection?

Feondi includes the REST API and available platform integrations. The monthly net rate per property depends on the total booked quantity. You can calculate the amount on the pricing page.