Open Connectivity, then Sales channels and API partners. Choose Partner accounts to set which properties a partner can sell and issue its API credentials. For example, you can open your Antalya hotels to one partner while keeping your Bodrum hotels closed to it. Each account keeps its credentials, bookings and reconciliation together.
API partner, profiles, and open properties
Create one API partner for each partner relationship. Creating an API partner also creates its stable Default profile.
The Default profile starts with an explicit snapshot of the accommodation properties that are published at that moment. It is not a dynamic “all properties” rule: a property published later stays closed until you open it.
Create additional profiles when the same API partner needs distinct catalogue audiences. A new optional profile starts empty. Profiles may contain overlapping properties. A profile does not represent a source market, destination rule, rate rule, or traveller point of sale.
Each profile has an explicit list of open properties: the properties open to that profile. From the Open properties tab, you can:
- Open or close one property.
- Apply the same change to a selected group of properties.
- Use Open in bulk by country to review the matching published properties and open them explicitly.
Closing a property removes it from that profile's catalogue and availability results. It does not delete the property or close it in another profile.
Credentials belong to the API partner
One API partner can have several independently named credentials, for example separate production, certification, and disaster-recovery identities. Credentials belong to the API partner and never to a profile. The partner selects a profile in the API request; when it omits that choice, the Default profile is used.
Never reuse one credential across different API partners. Separate credentials preserve clear audit, revocation, and usage records.
Pick an authentication mechanism
| Mechanism | When it fits | What the partner sends |
|---|---|---|
| OAuth 2.0 | Recommended for modern integrations. | Exchange client_id and client_secret for a short-lived access token, then send the token on API calls. |
| HTTP Basic | Legacy integrations that require a fixed username and password. | Send username and password on every call. |
| API key | Lightweight machine-to-machine integrations. | Send one long-lived bearer key on every call. |
Secret material is shown once. It appears only when a credential is created or rotated. Store it in a secret manager before leaving the screen.
Scopes
The same scopes apply to every authentication mechanism:
| Scope | What it grants |
|---|---|
distribution:read |
Reference data, the selected profile's property catalogue, availability, and offer search. |
distribution:booking |
Prebook, book, account-wide booking reads, cancellation quote, and cancellation. |
New credentials receive both scopes by default. Use only
distribution:read for an integration that must never create or cancel a
booking.
What partners find in a destination search
With distribution:read, a partner searches a destination and receives the
available properties among the selected profile's open properties, each priced
for the stay. The partner can:
- Order the result by price, stars or guest score.
- Narrow it by stars, property type, theme, amenity, district, map area, guest score, price for the stay, meal plan or free cancellation.
- Ask for a count per filter option.
When the partner sends an order or a filter, the whole destination is ordered and the response states the true total. A search with neither returns results page by page, without a total. Each property carries its guest score. Your online shop's Recommended order and your curated boosts are never sent to partners. See Destination search.
Partner payment terms
An API partner's payment terms determine how it pays your organization. These are separate from the payment terms shown to a guest on the rate plan.
| Agreement | Booking result |
|---|---|
| Settlement on account | Eligible prepaid, deposit and virtual-card rates are invoiced to the partner under its agreed terms. The partner does not make the guest payment through this booking request. |
| Pay at the property, or no on-account agreement | These rates are refused. Opening a property to the partner does not make every rate bookable. |
| Tours, transfers, flights and packages | Partner bookings require on-account terms. A package still keeps each component's payment obligations toward its supplier. |
For example, a 200 EUR prepaid stay can be confirmed against an on-account partner's agreement. That confirmation does not mean the partner has already paid you. A pay-at-property stay keeps its own collection terms.
The terms used are retained on the booking. Later account changes do not rewrite earlier bookings. Confirm the settlement period, price basis and currency before opening sales; a partner's request cannot override them. Agreeing on-account terms does not by itself establish an enforced credit limit.
Request limits and growth
Before increasing partner traffic, review the applicable request limits with your contact at Adrasis. Your connection terms identify the covered operation or group of operations, request count or rate, account scope, and time window. Several operations can share one account allowance. Creating or rotating credentials, or adding profiles, does not create another allowance.
Review observed requests, channel errors, and traffic trends in Insights. Share the relevant period, affected channels, and expected increase when discussing a capacity change. The agreed connection terms determine the limit and any change to it.
Supply partners and channel managers apply separate limits to their own connections. An Adrasis capacity change does not change those provider limits.
Lifecycle controls
Manage credentials from the API partner's Credentials tab:
- Rotate replaces the secret while keeping the credential identity. Share the new secret through a secure channel.
- Disable temporarily refuses authentication and can be reversed.
- Revoke permanently ends the credential. Create a new credential if the integration must return later.
Credential and API partner status are checked on API requests. A disabled or revoked identity, including an OAuth token minted from it, stops working as the status change propagates.
Operator checklist
- Create or open the API partner.
- Review the Default profile and any additional profiles.
- Open the intended properties in each profile's open properties list.
- Create a separately named credential for each partner environment.
- Select the minimum scopes and copy the one-time secret securely.
- Confirm the covered operations and request limits with your Adrasis contact.
- Ask the partner to confirm the resolved profile and complete a content, search, booking, reconciliation, and cancellation test.
Where to next
- Configure connector integrations → Channels
- Common partner API use cases → Metasearch & B2B platforms
- How partners order and filter destination results → Destination search