Skip to content
For LLMsView as Markdown·

Amadeus ​

undefined

DetailValue
CategoryTravel
Base URLhttps://api.amadeus.com
AuthenticationOAuth2 Client Credentials
Endpoints7
Connector keyamadeus

Using Amadeus in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Amadeus from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
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

DetailValue
Operation IDflight_offers_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Amadeus connection from the Connection dropdown.
  3. In the Operation dropdown, select flight_offers_0.
  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 ​

Hotel Offers

DetailValue
Operation IDhotel_offers_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Amadeus connection from the Connection dropdown.
  3. In the Operation dropdown, select hotel_offers_1.
  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 ​

Locations

DetailValue
Operation IDlocations_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Amadeus connection from the Connection dropdown.
  3. In the Operation dropdown, select locations_2.
  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 ​

Airlines

DetailValue
Operation IDairlines_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Amadeus connection from the Connection dropdown.
  3. In the Operation dropdown, select airlines_3.
  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 ​

Activities

DetailValue
Operation IDactivities_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Amadeus connection from the Connection dropdown.
  3. In the Operation dropdown, select activities_4.
  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

DetailValue
Operation IDflight_delay_5
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Amadeus connection from the Connection dropdown.
  3. In the Operation dropdown, select flight_delay_5.
  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 ​

Booking

DetailValue
Operation IDbooking_6
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Amadeus connection from the Connection dropdown.
  3. In the Operation dropdown, select booking_6.
  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.