API reference
Not published yet
The endpoints of the Partner API are still being built. There is no reference here yet because there is nothing behind it — and a reference that describes routes you cannot call is worse than an empty page.
What will be here
A reference generated directly from the gateway's OpenAPI document, so it can never drift from the running service: every route with its parameters, request and response schemas, error types, required scope and whether it consumes a search — plus a “Try it” console that runs against the sandbox with your own test key.
Until then
The documentation already covers everything that is settled and will not change when the endpoints land — authentication, idempotency, quota accounting, settlement, webhook signatures, the sandbox and the error envelope. That is the part worth reading now; the route list is the easy part to add later.
OverviewWhat the Partner API covers, and the conventions it follows.AuthenticationAPI keys, environments, scopes and IP allow lists.IdempotencyWhy every POST needs an Idempotency-Key, and how replay works.Search quotaFree allowance, per-search fee and the quota headers.Settlement modesWho is merchant of record, per booking.WebhooksEvents, signature verification and retries.SandboxFree test environment and the six forced failures.Errors and versioningThe error envelope, retry rules and how /v1 evolves.
Getting told when it lands
- The first release of the endpoints will be announced in the changelog, together with the OpenAPI document.
- Partner admins are emailed for every entry that changes the API surface, so there is nothing to poll.
- If you are planning an integration and want to be on the pilot, talk to your Vacabee contact — early integrators get the spec and a sandbox key before general availability.