> For the complete documentation index, see [llms.txt](https://adrasis.gitbook.io/developer/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/developer/readme.md).

# Overview

Integrate hotels, vacation rentals, villas, and apartments through a single canonical REST API: property content, real-time availability and rates, prebook, book, and cancel.

The Distribution Partner API exposes one REST contract for hotels, vacation rentals, villas, and apartments. Clients do not branch by property type:

```
content  →  search  →  prebook  →  book  →  (poll)  →  cancel
```

* **Content:** Ingest and cache property catalogue: descriptions, photos, room types, geo, policies. Delta-synced.
* **Search:** Compare 1..100 properties with exact top-1 bulk search, or inspect up to twenty exact allocations through the single-property detail route.
* **Prebook:** Send the chosen allocation's opaque `selection_token` to revalidate its sealed slots and lock price + cancellation policy behind a short-lived token.
* **Book:** Finalize the reservation idempotently.
* **Cancel:** Quote the penalty, then cancel.

The same search → prebook → book sequence applies to three other verticals: [Transfers](/developer/transfers.md), [Tours](/developer/tours.md), and [Flights](/developer/flights.md).

Two or more selected offers can be sold **as one contract**. [Package booking](/developer/package-booking.md) composes them into a single atomic booking with one inclusive price: either every service confirms, or nothing does. If instead you only need to group bookings you already confirmed, keeping their separate totals and lifecycles, use [Trip bundling](/developer/trip-bundling.md).

## Base URL

```
https://ari.console.adrasis.com/api/v1
```

All field names are `snake_case`, all dates are ISO 8601, all currencies are ISO 4217, and every resource is addressed by its opaque `public_id`.

## Where to start

1. [Getting started](/developer/getting-started.md): Obtain credentials and make your first authenticated call.
2. [Authentication](/developer/authentication.md): Use the OAuth 2.0 client-credentials flow.
3. [Property content](/developer/property-content.md): Build and refresh your catalogue.
4. [Currencies, occupancy & allocations](/developer/currencies-occupancy-allocations.md): Choose bulk or detail and express strict or flexible occupancy.
5. [The booking flow](/developer/booking-flow.md): Follow search → prebook → book → cancel.
6. [Transfers](/developer/transfers.md), [Tours](/developer/tours.md), [Flights](/developer/flights.md): The other product verticals follow the same three-step sequence.
7. [Package booking](/developer/package-booking.md): Sell several services as one atomic, single-price booking.
8. [Trip bundling](/developer/trip-bundling.md): Group confirmed bookings into one trip.
9. [Booking webhooks](/developer/booking-webhooks.md): Receive signed lifecycle events.
10. [API reference](/developer/api-reference.md): Use the interactive specification.

Building an AI agent? See [AI agent integration (MCP)](/developer/ai-agents-mcp.md). The published site also serves an LLM-readable index at `/llms.txt`.


---

# 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/developer/readme.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.