> For the complete documentation index, see [llms.txt](https://adrasis.gitbook.io/console/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adrasis.gitbook.io/console/distribution/outbound/partner-api-credentials.md).

# Partner Network and API credentials

Use **Partner Network → Partner Accounts** to decide which properties a technical partner can discover and to issue the credentials it uses for the Distribution API. A partner account is the stable boundary for authentication, property publication, booking references, and reconciliation.

## Account, profiles, and Channel Portfolio

Create one partner account for each technical partner relationship. Creating an account 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 partner profiles when the same 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's **Channel Portfolio** is the explicit set of properties open to that profile. From **Profiles & Channel Portfolio**, you can:

* Open or close one property.
* Apply the same change to a selected group of properties.
* Build a snapshot from country or place filters, review the matches, 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 account

One partner account can have several independently named credentials, for example separate production, certification, and disaster-recovery identities. Credentials belong to the account 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 partner accounts. 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.                                                              |

{% hint style="warning" %}
**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.
{% endhint %}

## 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 of the selected profile's Channel Portfolio, 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](/console/bookings/destination-search.md).

## 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](/console/insights/insights.md). 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 account's **API Access** 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 account 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

1. Create or open the partner account.
2. Review the Default profile and any additional profiles.
3. Open the intended properties in each Channel Portfolio.
4. Create a separately named credential for each partner environment.
5. Select the minimum scopes and copy the one-time secret securely.
6. Confirm the covered operations and request limits with your Adrasis contact.
7. 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](/console/distribution/channels.md)
* **Common partner API use cases** → [Metasearch & B2B platforms](/console/distribution/outbound/metasearch.md)
* **How partners order and filter destination results** → [Destination search](/console/bookings/destination-search.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://adrasis.gitbook.io/console/distribution/outbound/partner-api-credentials.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.