Overview
This node integrates with the Seats.aero API to retrieve detailed flight information. Specifically, the Get Trips operation fetches flight-level details for a given trip identified by its Trip ID. This is useful when you have an availability object or search result and want to obtain comprehensive data about a specific trip, such as flight segments, timings, and other metadata.
Common scenarios:
- After searching for available flights, use this node to get detailed itinerary information for a selected trip.
- Automate retrieval of trip details for booking systems or travel management platforms.
- Enrich trip data with additional attributes before further processing or reporting.
Example:
You have a Trip ID from a previous search and want to fetch all flight segments and timing details for that trip to display to a user or process in your workflow.
Properties
| Name | Meaning |
|---|---|
| Trip ID | The unique identifier of the trip to retrieve detailed flight-level information for. |
Output
The node outputs a JSON object under the json field with the following structure:
{
"success": true,
"data": { /* full trip details as returned by Seats.aero API */ }
}
success: A boolean indicating if the API call was successful.data: Contains the detailed trip information including flight segments, times, and related metadata as provided by the Seats.aero API.
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
Partner-Authorization.
Troubleshooting
- Missing or invalid Trip ID: The Trip ID property is required. Ensure it is provided and correctly formatted.
- Authentication errors: Verify that the API key credential is set up correctly and has the necessary permissions.
- Network or API errors: Check network connectivity and confirm the Seats.aero API service is operational.
- Unexpected response format: If the API changes, the node might not parse responses correctly; verify API version compatibility.
Links and References
- Seats.aero API Documentation (official API docs)
- n8n documentation on creating custom nodes