Appearance
Amadeus
undefined
| Detail | Value |
|---|---|
| Category | Travel |
| Base URL | https://api.amadeus.com |
| Authentication | OAuth2 Client Credentials |
| Endpoints | 7 |
| Connector key | amadeus |
Using Amadeus in a workflow
- Go to Connections and click New Connection.
- Pick Amadeus 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 | Flight Offers |
GET | Hotel Offers |
GET | Locations |
GET | Airlines |
GET | Activities |
GET | Flight Delay |
GET | Booking |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Flight Offers
| Detail | Value |
|---|---|
| Operation ID | flight_offers_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amadeus connection from the Connection dropdown.
- In the Operation dropdown, select
flight_offers_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 Amadeus API reference.
GET
Hotel Offers
| Detail | Value |
|---|---|
| Operation ID | hotel_offers_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amadeus connection from the Connection dropdown.
- In the Operation dropdown, select
hotel_offers_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 Amadeus API reference.
GET
Locations
| Detail | Value |
|---|---|
| Operation ID | locations_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amadeus connection from the Connection dropdown.
- In the Operation dropdown, select
locations_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 Amadeus API reference.
GET
Airlines
| Detail | Value |
|---|---|
| Operation ID | airlines_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amadeus connection from the Connection dropdown.
- In the Operation dropdown, select
airlines_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 Amadeus API reference.
GET
Activities
| Detail | Value |
|---|---|
| Operation ID | activities_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amadeus connection from the Connection dropdown.
- In the Operation dropdown, select
activities_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 Amadeus API reference.
GET
Flight Delay
| Detail | Value |
|---|---|
| Operation ID | flight_delay_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amadeus connection from the Connection dropdown.
- In the Operation dropdown, select
flight_delay_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 Amadeus API reference.
GET
Booking
| Detail | Value |
|---|---|
| Operation ID | booking_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amadeus connection from the Connection dropdown.
- In the Operation dropdown, select
booking_6. - 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 Amadeus API reference.