Your contracts, bookableGet a quote

Let partner systems search, quote and book your contracts.

The partner API is a travel booking API for DMCs. Each partner system you approve searches your inventory, gets a quote and creates a booking, at sell prices only. Every partner has its own client, environment and scopes, and the documentation is generated from the API itself.

  • Search, quote, bookfrom your approved inventory
  • Sell prices onlynet cost and margin stay with you
  • In every planafter a review, for eligible clients
One client per partner, each with its own environment and scopes. Illustrative.

What a partner system can do through the partner API

The partner API gives a partner's own system secure access to your rates and bookings. It reads from your live inventory, the same merged catalogue your search, proposals and bookings use, and never from raw contracts.

  • 1
    Search

    Hotels and rates for a destination, dates and party, from inventory you have approved.

  • 2
    Quote

    A priced stay from the same engine that prices your team's quotes, so the number matches.

  • 3
    Book

    The booking lands in your bookings list, tracked from request to confirmation like any other.

Search, quote and book, in three calls against your inventory. Illustrative.

Sell prices only: your net cost and margin never leave

Partners receive the price your pricing engine produces after your margin is applied. The net rate from the contract and the margin on top stay inside your account.

One quote, two views

Azure Cove Resort · Ocean Room · HB · 7 nights

LineYour teamPartner
Net costUSD 1,964.00not sent
Your marginUSD 346.00not sent
Sell priceUSD 2,310.00USD 2,310.00

Illustrative figures.

One engine, every channel

A stay is priced the same way in search, in a proposal and through the API, with your margin, approval limits and currency on top. See how pricing works.

One client per partner, with its own scopes

The Partner API is in every plan; access is switched on after a review, for eligible clients. Then you decide who connects and what they may do. Each partner system gets its own client, set to sandbox or production, with scopes that limit it to reading rates or also writing bookings.

  • 1
    Sandbox or production

    Issue a sandbox client for testing and a separate production client when the partner goes live.

  • 2
    Scopes per partner

    rates:read for a partner that only shows your rates; add bookings:write when it may book.

  • 3
    Short-lived tokens

    The partner trades its client ID and secret for an OAuth2 bearer token that expires after one hour.

Credentials in, a one-hour token out. Illustrative values.
Partner clients: two partner systems, one in sandbox with read access to rates and one in production with rates and booking access, each with its client ID and status. (opens the full-size screenshot in a new tab)
Each partner gets its own client, environment and scopes: rates only, or rates and bookings.

Developer documentation that cannot drift

A partner's developers get a reference built from the API itself: 22 endpoints in three groups, authentication, rates and hotels, and bookings, each with an example request. When the API changes, the reference changes with it.

  • 1
    Import and call

    A Postman collection and OpenAPI files in JSON and YAML, ready for a partner's own tooling.

  • 2
    Browse in Swagger UI

    Every endpoint and its parameters, readable in the browser.

  • 3
    Versioned

    v2 is current and v1 stays documented as legacy, each listed separately.

Generated from the API, so the reference matches what partners call.
Partner API documentation: endpoint reference grouped into authentication, rates and hotels, and bookings, with an example token request and downloads for a Postman collection and OpenAPI files. (opens the full-size screenshot in a new tab)
Developer documentation generated from the API itself: endpoints, examples, Postman and OpenAPI.

Webhooks for the events you push out

The API lets partners pull. Webhooks push: when something happens in your account, such as a booking confirmed, a customer created or a contract approved, an HTTP notification goes to an endpoint you name, as it happens.

  • 1
    One event per webhook

    Each webhook listens for one event across contracts, inventory, proposals, bookings, customers or team changes; point several at one endpoint to hear more.

  • 2
    Signed and retried

    Deliveries are signed so the receiver can check they came from you, and failed deliveries are retried.

  • 3
    Testable and observable

    Send a test before relying on a webhook, then read each delivery and its payload in the log.

Webhooks are part of the platform's extensibility layer. Connecting a specific product on the receiving side is scoped with you; see how integrations are scoped.

Each event, where it went and what happened. Illustrative.
Webhooks: outbound HTTP notifications for events such as booking confirmed, customer created, inventory synced and contract approved, each with its endpoint and delivery log. (opens the full-size screenshot in a new tab)
Webhooks push real events to your other systems, with deliveries you can inspect.

B2B portal for partner agents: coming soon

Not every partner has a system that can call an API. For their agents, a B2B portal is in development: a login under your brand where they search, quote and book the same inventory, at the same sell prices the partner API returns.

  • 1
    Search, quote and book

    Partner agents self-serve on your inventory instead of emailing your team for each quote.

  • 2
    Your brand at the door

    Your logo and name on the login, so partners deal with you, not a software vendor.

  • 3
    An agency CRM view

    Each agency's profile, communication and performance in one place, for your account team.

Coming soon

A preview of the planned portal. Not available yet; illustrative.

Questions about the partner API

What can a partner system do through the API?

Search hotels and rates, get a quote for a stay and create a booking, then read that booking back. Every answer comes from your approved inventory, never from raw contracts.

Does a partner ever see my net rates or margin?

No. The API returns sell prices only: the price your pricing engine produces once your margin is applied. Net cost and margin stay in your account.

Is the Partner API in every plan?

Yes. The Partner API is included in every plan. Access is switched on after a review, for eligible clients.

How does a partner get access?

You add the partner as a client, choose sandbox or production and grant scopes such as rates:read or bookings:write. The partner exchanges its client ID and secret for a bearer token that lasts one hour.

Where do bookings made through the API show up?

In your bookings list, next to bookings created from proposals and from search, tracked from request through confirmation, cancellation or rejection.

Which events can webhooks send?

Events across contracts, hotel inventory, proposals, bookings, customers and team changes, such as booking confirmed or contract approved. One webhook listens for one event; point several at the same endpoint to hear more.

Is there a B2B portal for partner agents?

Not yet. A branded portal where partner agents search, quote and book under your brand, with an agency CRM view, is coming soon. We will not give a date until it is ready.

Let your partners book what you sell

Bring a contract and the partner that wants to connect. On the call we load the rates and walk through the client, scopes and documentation that partner would get.

Get a quoteOpens the quote engine. Plans are sized by contract volume and quoting activity.
Schedule a demoA 30-minute call. We load your contract live and build a quote from it.