# OTA Connection Guide

[FR](/kribos-docs/guides-clients/gitbook-guide-connexion-ota-gitbook-native.md) | [EN](/kribos-docs/guides-clients/gitbook-ota-connection-guide-en.md)

![Connect your OTAs without technical setup](/files/y8eOFwlq6Rx5eGnx87L9)

> **KribOS client guide**
>
> Connect Booking.com, Airbnb, Expedia, VRBO, Agoda, Trip.com, Hotelbeds and other reservation platforms to KribOS without technical setup on the host side.

> **Activation time**
>
> After you submit a connection request, KribOS verifies the information and gets back to you within **24 business hours**. Some platforms may also require validation inside their own extranet.

## At a glance

| What KribOS syncs | Why it matters                                                           |
| ----------------- | ------------------------------------------------------------------------ |
| **Availability**  | Reserved or blocked dates in KribOS are sent to the connected platforms. |
| **Reservations**  | New reservations are centralized in your KribOS workspace.               |
| **Support**       | KribOS guides you when an action is required inside an OTA extranet.     |

![OTA connection workflow](/files/VAjhgakeEEP9xc559akP)

## Two possible scenarios

![Two OTA activation scenarios](/files/TghRMf9UlHPy2Z6jxsn0)

### Scenario A - You already have OTA listings

Choose this path if your properties already exist on Booking.com, Airbnb, Expedia, VRBO or another platform.

1. KribOS retrieves the available information from the platform or from the identifiers you provide.
2. You validate the mapping: which OTA listing matches which KribOS property.
3. KribOS checks rooms, rates and availability.
4. Synchronization is activated after verification.

This scenario is useful when your listings already exist and you want to avoid recreating everything manually.

### Scenario B - You create your properties in KribOS first

Choose this path if you want to start clean from KribOS, or if your properties are not structured yet.

1. You add your properties, rooms or units in KribOS.
2. You then add the OTA identifiers or listing links you have.
3. The KribOS team prepares the matches with the platforms.
4. KribOS finalizes the activation with you.

This scenario is useful if you want to use KribOS as the central source before connecting the OTAs.

> **Key point**
>
> Mapping is always validated before activation. This prevents an OTA listing from being linked to the wrong KribOS property.

## OTA commissions and fees

KribOS does not change the commissions applied by your OTAs. Booking.com, Airbnb, Expedia and other platform commissions depend on your contract with each platform.

Channex acts as the connectivity layer between KribOS and OTAs. Channex documentation shows that bookings may include an `ota_commission` field, meaning the commission information provided by the OTA for a booking. This does not mean that Channex creates a new commission for the host.

For direct reservations through a booking engine, Channex states that its Instant Booking Page is free to use and has no costs or fees. In KribOS, the applicable commercial terms remain your KribOS subscription and your OTA contracts.

Sources:

* [Channex - Bookings Collection](https://docs.channex.io/api-v.1-documentation/bookings-collection)
* [Channex - Instant Booking Page / Booking Engine](https://help.channex.io/en/articles/8275292-instant-booking-page-booking-engine)
* [Channex - About and FAQ](https://docs.channex.io/about-channex-and-faq)

## Before you start

Prepare this information for each platform you want to connect:

| Information            | Example                           | Where to find it            |
| ---------------------- | --------------------------------- | --------------------------- |
| Platform name          | Booking.com, Airbnb, Expedia      | Your OTA account            |
| Listing or property ID | Property ID, Listing ID, Hotel ID | OTA extranet or listing URL |
| Property name          | Riad Atlas Marrakech              | KribOS or your OTA          |
| OTA account email      | <host@example.com>                | Email used for the platform |

> **Important**
>
> Never share your OTA password with KribOS. We only ask for the identifiers needed for the connection, or we guide you through authorizing the connection from the OTA extranet.

## Connection journey

![KribOS and OTA sync sequence](/files/MHKpN3DGE2HNrJ351yP4)

### Step 1 - Choose the platform

In KribOS, open **Reservation platforms**, then search for the OTA you want to connect.

### Step 2 - Add the information

Enter the listing ID, property name and OTA account email if available.

### Step 3 - Send the request

Click **Send request**. The request will then appear in **Connection tracking**.

### Step 4 - Wait for KribOS confirmation

KribOS verifies the information, prepares the connection and gets back to you within **24 business hours**.

> **Connection active**
>
> Once the connection is active, availability and reservations are synchronized automatically according to the platform capabilities.

## What the KribOS screen looks like

### Platform card

| Platform        | Description                                                                      | Action      |
| --------------- | -------------------------------------------------------------------------------- | ----------- |
| **Booking.com** | Usually available in your Booking.com extranet, inside the property information. | **Connect** |
| **Airbnb**      | The listing ID is often visible in the listing URL after `/rooms/`.              | **Connect** |
| **Expedia**     | The property ID is available in Expedia Partner Central.                         | **Connect** |

### Status example

| Property             | Platform    | Status       | Message                                                                        |
| -------------------- | ----------- | ------------ | ------------------------------------------------------------------------------ |
| Riad Atlas Marrakech | Booking.com | Request sent | KribOS verifies the information and gets back to you within 24 business hours. |

## Activation timing

| Case                                               | Indicative timing                                           |
| -------------------------------------------------- | ----------------------------------------------------------- |
| Correct identifier and no external action required | Fast activation after verification                          |
| Validation required in the OTA extranet            | Depends on how quickly the platform validation is completed |
| Missing information or incorrect identifier        | KribOS asks you to correct the information                  |
| Regional or less common platform                   | Availability check before activation                        |

## Possible statuses

| Status in KribOS         | Meaning                                                            |
| ------------------------ | ------------------------------------------------------------------ |
| **Request sent**         | KribOS has received your request and is verifying the information. |
| **Host action required** | You need to validate an action inside the platform extranet.       |
| **Configuration**        | KribOS is linking your listing to your property.                   |
| **Connected**            | Synchronization is active.                                         |
| **Needs correction**     | Information is missing or needs to be updated.                     |
| **Blocked**              | The connection cannot be completed without intervention.           |

## Available platforms

| Main OTAs    | Additional OTAs      |
| ------------ | -------------------- |
| Booking.com  | Agoda                |
| Airbnb       | Trip.com / Ctrip     |
| Expedia      | Despegar             |
| VRBO         | Hotelbeds            |
| Google Hotel | Hostelworld          |
|              | Hopper               |
|              | HRS                  |
|              | HyperGuest           |
|              | Klook                |
|              | MakeMyTrip / Goibibo |
|              | Traveloka            |
|              | Tiket.com            |
|              | OpenGDS              |
|              | Feratel              |
|              | Other platform       |

> **Platform not listed**
>
> If your platform is not listed, choose **Other platform** and add the OTA name, listing link or any available identifier.

## Quick guide by platform

### Booking.com

Requested information: **Booking.com Property ID**

You can usually find it in the Booking.com extranet, inside the property information.

Possible actions:

1. Open Booking.com Extranet.
2. Go to connectivity settings.
3. Choose KribOS as the connectivity provider if the option is available.
4. Send the request in KribOS.

### Airbnb

Requested information: **Airbnb Listing ID**

You can often find it in the listing URL, after `/rooms/`.

Possible actions:

1. Open your Airbnb host dashboard.
2. Check the listing ID.
3. Send the request in KribOS.
4. KribOS will tell you if an additional authorization is required.

### Expedia / VRBO

Requested information: **Expedia or VRBO Property ID**

Possible actions:

1. Open Expedia Partner Central or your VRBO portal.
2. Check the property ID.
3. Activate the connectivity provider if the platform asks you to.
4. Send the request in KribOS.

### Agoda

Requested information: **Agoda Hotel ID**

You can find it in Agoda YCS.

### Other platform

Requested information:

* platform name;
* listing link if available;
* hotel, listing or account identifier if available;
* email used on the platform.

KribOS will check whether the connection is available and respond within **24 business hours**.

## Best practices

* Connect your most important platforms first.
* Make sure your OTA listings match the correct KribOS properties.
* Avoid changing prices or availability in multiple tools during activation.
* Keep access to your OTA extranets during configuration.
* Tell KribOS about any important future reservation that has not been imported yet.

## FAQ

### Are my existing reservations imported automatically?

It depends on the platform. Some platforms allow future existing reservations to be retrieved, while others require manual verification. KribOS will confirm the expected behavior during activation.

### Do I need to share my OTA password with KribOS?

No. Never share your OTA password. KribOS only asks for the identifiers needed for the connection, or guides you through authorizing the connection from the extranet.

### Is synchronization immediate?

Once the connection is active, availability and reservation updates are synchronized automatically. During the request phase, allow up to **24 business hours** for KribOS verification.

### What should I do if I cannot find my identifier?

Send the request with the platform name and listing link. KribOS will help you find the correct information.

## Pre-activation checklist

* [ ] The property exists in KribOS.
* [ ] The listing exists on the OTA platform.
* [ ] The listing or property identifier is available.
* [ ] The OTA account email is known.
* [ ] Important future reservations have been reported to KribOS.
* [ ] You can access the OTA extranet if validation is required.

## KribOS visual direction for GitBook

Use these colors for all GitBook blocks and visuals:

| Element              | Recommendation                                 |
| -------------------- | ---------------------------------------------- |
| Page title           | `Connect your reservation platforms to KribOS` |
| Visual CTA           | KribOS Terracotta `#B85A3B`                    |
| Light terracotta     | `#F7E9E2`                                      |
| Soft background      | Sand `#FAFAF7`                                 |
| Secondary background | Sage `#F1F3EE`                                 |
| Primary text         | Ink `#141412`                                  |
| Secondary text       | Muted ink `#62645D`                            |
| Borders              | `#DFE3D8`                                      |
| Success accent       | Green `#3B7F5D`                                |
| Attention accent     | Gold `#9A7835`                                 |


---

# Agent Instructions: 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:

```
GET https://kribos.gitbook.io/kribos-docs/guides-clients/gitbook-ota-connection-guide-en.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.