> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/integrations/online-travel-agencies-ota.md).

# Online Travel Agencies (OTA)

## Online Travel Agencies (OTA)

Guestway supports direct **Online Travel Agency (OTA)** integrations. These integrations work alongside your existing Property Management System (PMS) integration to give you faster communication and more control without leaving the platform.

**Important**: OTA integrations are always supplementary to a PMS. An organization cannot have only OTA integrations without any PMS integrations — connect a PMS first.

## Advantages

Adding an OTA integration directly brings several benefits, depending on your PMS:

* **Faster communication** — receiving and sending messages is faster and often instant.
* **More actions in one place** — some actions become directly available in Guestway, whereas before you had to go to the PMS or OTA website.
* **Extended review support** — Review center support is extended with more features than before.

## Supported OTA integrations

{% content-ref url="/pages/ht0VLFCGavo8AWPhTZ84" %}
[Airbnb](/integrations/online-travel-agencies-ota/airbnb.md)
{% endcontent-ref %}

{% content-ref url="/pages/kBJtMtDFZjVd4zhbiUzV" %}
[Booking.com](/integrations/online-travel-agencies-ota/booking.com.md)
{% endcontent-ref %}

{% content-ref url="/pages/bh24NdVJZnQHYjlAfTYt" %}
[Expedia](/integrations/online-travel-agencies-ota/expedia.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/integrations/online-travel-agencies-ota.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.