Actions44
- Contact Actions
- Aircraft Actions
- Get
- Get List
- Get by Registration
- Get Identification
- Get Status
- Get Maintenance
- Get Flights
- Get APU
- Get Avionics
- Get Engine
- Get Airframe
- Get Additional Equipment
- Get Features
- Get Interior
- Get Exterior
- Get Leases
- Get Company Relationships
- Get Pictures
- Get Bulk Aircraft Export Paged
- Get Condensed Owner Operators Paged
- Get Event List Paged
- Get History List Paged
- Company Actions
- Market Actions
Overview
This node interacts with the JetNet API to retrieve paginated aircraft history data. It is designed to fetch detailed historical records related to specific aircraft, supporting pagination to handle large datasets efficiently. This functionality is useful for aviation industry professionals who need to analyze or audit the history of aircraft, such as maintenance events, ownership changes, or other significant transactions.
Practical examples include:
- Retrieving a specific page of an aircraft's history list to review recent maintenance or ownership events.
- Integrating aircraft history data into aviation management systems for compliance and record-keeping.
- Automating periodic checks on aircraft history updates by iterating through pages.
Properties
| Name | Meaning |
|---|---|
| Page Size | Number of results per page (minimum 1, maximum 1000). Controls how many history records are returned in one request. |
| Page | Page number to retrieve (minimum 1). Specifies which page of the paginated history list to fetch. |
Output
The output is a JSON array where each item represents an individual aircraft history record retrieved from the JetNet API. Each record contains detailed information about a specific historical event or transaction related to the aircraft.
The structure of each JSON object corresponds directly to the data returned by the JetNet API's /api/Aircraft/getHistoryListPaged endpoint, typically including fields such as dates, descriptions, transaction types, involved parties, and other relevant metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the JetNet API via a configured API key credential.
- The node uses HTTP POST requests to the JetNet API endpoint
https://customer.jetnetconnect.com/api/Aircraft/getHistoryListPaged/{apiToken}/{pageSize}/{page}. - Proper API authentication token must be provided in the node credentials.
- Network access to the JetNet service is necessary.
Troubleshooting
Common issues:
- Invalid or expired API token: The API will reject requests if the authentication token is invalid or expired. Ensure the API key credential is up to date.
- Exceeding page size limits: The API enforces a maximum page size of 1000. Setting a higher value may cause errors.
- Requesting non-existent pages: Requesting a page number beyond the available data range may return empty results.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate issues with the API token; re-authenticate or update credentials.
- Validation errors may occur if
pageSizeorpageparameters are out of allowed ranges. - Timeout or network errors suggest connectivity issues; verify network settings and API availability.
Links and References
- JetNet API Documentation (requires login)
- n8n documentation on HTTP Request Node for understanding API interactions
- Aviation industry resources for aircraft history and maintenance tracking