Seats.aero icon

Seats.aero

Interact with Seats.aero API

Actions3

Overview

The node interacts with the Seats.aero API to retrieve flight availability data. Specifically, the Bulk Availability operation allows users to fetch a large volume of availability objects filtered by a specific mileage program and other criteria such as cabin class, date range, and geographic regions.

This node is beneficial for travel agencies, airline partners, or developers building applications that require comprehensive access to award seat availability across multiple routes and dates. For example, it can be used to:

  • Bulk download award seat availability for a loyalty program to analyze trends.
  • Power search tools that show available flights in different cabins between regions.
  • Aggregate availability data for inventory management or customer booking assistance.

Properties

Name Meaning
Mileage Program The specific mileage program (loyalty program) from which to retrieve availability data.
Cabin The cabin class filter for results. Options: Economy, Premium, Business, First.
Start Date The start date (YYYY-MM-DD) for the availability search window.
End Date The end date (YYYY-MM-DD) for the availability search window.
Origin Region The geographic region of origin airports. Options: Africa, Asia, Europe, North America, Oceania, South America.
Destination Region The geographic region of destination airports. Same options as Origin Region.
Cursor A numeric cursor for pagination to continue fetching results from a previous query.
Take Number of results to return, minimum 10 and maximum 1000.
Skip Number of results to skip, useful for pagination.

Output

The node outputs JSON data under the json field structured as follows:

{
  "success": true,
  "data": { /* response body from Seats.aero bulk availability endpoint */ }
}
  • success: Boolean indicating if the API call was successful.
  • data: Contains the raw availability data returned by the Seats.aero API. This includes availability objects matching the specified filters.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Seats.aero partner API.
  • The base URL for API requests is https://seats.aero/partnerapi.
  • The API key must be provided in the request header Partner-Authorization.

Troubleshooting

  • Common issues:

    • Missing or invalid API key will cause authentication failures.
    • Providing invalid date formats or out-of-range values for take may result in API errors.
    • Pagination parameters (cursor, skip) must be used carefully to avoid missing or duplicating data.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate problems with the API key; verify the credential configuration.
    • Validation errors from the API may mention invalid parameter values; check all inputs especially dates and numeric limits.
    • Rate limiting or quota exceeded errors may occur if too many requests are made in a short time; implement retry logic or reduce request frequency.

Links and References

Discussion