Overview
The node interacts with the Seats.aero API to retrieve cached flight search results based on specified criteria such as origin and destination airports, travel dates, cabin class, and sorting preferences. This operation is useful for quickly accessing pre-cached flight availability data without performing a fresh search, which can save time and reduce API load.
Common scenarios include:
- Quickly fetching available flights between specific airports within a date range.
- Filtering results by cabin class (Economy, Premium, Business, First).
- Sorting results by departure date or lowest mileage required.
- Paginating through large result sets using cursor, skip, and take parameters.
Practical example: A travel agency workflow that needs to display available award flights from San Francisco (SFO) to London Heathrow (LHR) in business class for a given week, sorted by departure date.
Properties
| Name | Meaning |
|---|---|
| Origin Airport | Comma-delimited list of origin airport codes (e.g., "SFO,LAX"). Required. |
| Destination Airport | Comma-delimited list of destination airport codes (e.g., "FRA,LHR"). Required. |
| Cabin | Cabin class filter for results. Options: Economy, Premium, Business, First. Default: Economy. |
| Start Date | Start date of travel period in YYYY-MM-DD format. |
| End Date | End date of travel period in YYYY-MM-DD format. |
| Cursor | Numeric cursor for pagination to indicate the position in the result set. |
| Take | Number of results to return. Minimum 10, maximum 1000. |
| Order By | Sort order of results. Options: Departure Date, Lowest Mileage. Default: Departure Date. |
| Skip | Number of results to skip (offset) for pagination. |
Output
The output JSON contains two main fields:
success: A boolean indicating whether the API request was successful.data: The body of the response from the Seats.aero API containing the cached search results. This typically includes flight availability details matching the query parameters.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Seats.aero partner API.
- The base URL used for requests is
https://seats.aero/partnerapi. - The API key must be provided in the request header under
Partner-Authorization.
Troubleshooting
- Missing or invalid API key: The node will fail if the API key credential is not set or invalid. Ensure the correct API key is configured.
- Invalid airport codes: Providing incorrect or unsupported IATA airport codes may result in empty or error responses.
- Date format errors: Dates must be in YYYY-MM-DD format; otherwise, the API may reject the request.
- Pagination issues: Using cursor, skip, or take values outside allowed ranges may cause unexpected results or errors.
- API rate limits: Frequent requests might hit API rate limits; consider adding delays or caching results.
Links and References
- Seats.aero API Documentation (hypothetical link for reference)
- IATA Airport Codes: https://www.iata.org/en/publications/directories/code-search/
- ISO 8601 Date Format: https://en.wikipedia.org/wiki/ISO_8601