Appearance
Booking.com
undefined
| Detail | Value |
|---|---|
| Category | Travel |
| Base URL | https://supply-xml.booking.com/hotels/xml |
| Authentication | API Key |
| Endpoints | 6 |
| Connector key | booking-com |
Using Booking.com in a workflow
- Go to Connections and click New Connection.
- Pick Booking.com from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Hotels |
GET | Rooms |
GET | Availability |
GET | Rates |
GET | Reservations |
GET | Cities |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Hotels
| Detail | Value |
|---|---|
| Operation ID | hotels_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Booking.com connection from the Connection dropdown.
- In the Operation dropdown, select
hotels_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Booking.com API reference.
GET
Rooms
| Detail | Value |
|---|---|
| Operation ID | rooms_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Booking.com connection from the Connection dropdown.
- In the Operation dropdown, select
rooms_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Booking.com API reference.
GET
Availability
| Detail | Value |
|---|---|
| Operation ID | availability_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Booking.com connection from the Connection dropdown.
- In the Operation dropdown, select
availability_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Booking.com API reference.
GET
Rates
| Detail | Value |
|---|---|
| Operation ID | rates_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Booking.com connection from the Connection dropdown.
- In the Operation dropdown, select
rates_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Booking.com API reference.
GET
Reservations
| Detail | Value |
|---|---|
| Operation ID | reservations_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Booking.com connection from the Connection dropdown.
- In the Operation dropdown, select
reservations_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Booking.com API reference.
GET
Cities
| Detail | Value |
|---|---|
| Operation ID | cities_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Booking.com connection from the Connection dropdown.
- In the Operation dropdown, select
cities_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Booking.com API reference.