Skip to content
Nappai Documentation

Amadeus API

The Amadeus API component lets you pull travel information from Amadeus into your Nappai workflow.
Choose the type of search you need—flights, hotels, locations, or activities—provide the required data, and the component returns the results as a Data object that can be used by other components.

How it Works

When you add the component to a dashboard, you first configure a Credential that contains your Amadeus Client ID and Client Secret.
After selecting the credential, you choose an Api Selection (Flight Offers Search, Hotel Search, Location Search, or Activity Search).
The component then takes the input data you provide, calls the corresponding Amadeus API endpoint, and attaches the returned information to the input record.
The final output is a list of Data objects, each enriched with a new field (flights, hotels, locations, or activities) that holds the API response.

Inputs

Input

Input: The data record(s) that will be sent to the Amadeus API.

  • For a flight search, include origin, destination, and depart_date.
  • For a hotel search, include city_code, and optionally rating and radius_km.
  • For a location search, include keyword, subtype, and countryCode.
  • For an activity search, include latitude, longitude, and radius.

Api Selection

Api Selection: Choose which Amadeus API you want to call.

  • Flight Offers Search
  • Hotel Search
  • Location Search
  • Activity Search

Default Currency

Default Currency: Pick the currency that the API should use for prices (e.g., EUR, USD, GBP).

Default Language

Default Language: Pick the language for the API responses (e.g., en-US, es-ES).

Credential

Credential: Select the Amadeus Travel API credential that you have previously set up in Nappai.

Important:

  1. First, create an Amadeus Travel API credential in the Nappai credentials section.
  2. Then, choose that credential in the component’s Credential field.

Outputs

Data: The component returns a list of Data objects.
Each input record is enriched with a new field that contains the API response:

  • flights for flight searches
  • hotels for hotel searches
  • locations for location searches
  • activities for activity searches

These Data objects can be passed to other components, displayed in dashboards, or stored for later use.

Usage Example

  1. Create a credential

    • Go to Credentials → Add Credential → Amadeus Travel API.
    • Enter your Amadeus Client ID and Client Secret.

  2. Add the Amadeus API component

    • Drag the component onto the canvas.
    • In the Credential field, select the credential you just created.
    • Set Api Selection to Flight Offers Search.
    • Choose Default Currency (e.g., USD) and Default Language (e.g., en-US).

  3. Provide input data

    • Create a Data record with origin: "NYC", destination: "LON", depart_date: "2025-12-01".
    • Connect this record to the component’s Input field.

  4. Run the workflow

    • The component calls Amadeus, retrieves the cheapest flight offers, and returns a Data object that now contains a flights field with the results.

  5. Use the results

    • Connect the output to a Table component to display the flight offers, or to a Decision component to filter by price.
  • Google Maps API – Retrieve maps, directions, and place details.
  • Travel Booking API – Book flights, hotels, or activities directly from your workflow.
  • Data Formatter – Clean and transform the data returned by Amadeus before using it elsewhere.

Tips and Best Practices

  • Validate input data before sending it to Amadeus to avoid API errors.
  • Use the default currency and language that match your target audience for consistent results.
  • Cache frequent queries if your workflow runs often to reduce API calls and improve performance.
  • Handle pagination if you expect large result sets; the component currently returns the first page only.

Security Considerations

  • Store your Amadeus credentials in Nappai’s secure credential store; never hard‑code them in your workflow.
  • Ensure that only authorized users have access to the credential and the component.
  • Monitor API usage to detect any unexpected spikes that could indicate misuse.