New: Single Aircraft History and Flight Data Endpoints
Description:
Added four new Customer API endpoints that allow authorized customers to retrieve aircraft history and flight data for a single aircraft:
· getAllAircraftHistoryByAircraftID
· getAllAircraftHistoryByAircraftIDPaged
· getAllFlightDataHistoryByAircraftID
· getAllFlightDataHistoryByAircraftIDPaged
Access to the Single Aircraft History and Single Aircraft Flight Data endpoints is managed separately based on the customer’s API subscription. Each endpoint group has its own daily request limit, with a default allowance of 100 calls per day per endpoint group. Custom daily limits may be configured based on the customer’s subscription.
Aircraft history requests do not reduce the allowance for flight data requests, and vice versa. Paged and non-paged requests share the allowance for their corresponding endpoint. Retrieving additional pages from the same request does not count as an additional API call.
Daily request limits reset at midnight Eastern Time. If a customer reaches an endpoint’s daily limit, the API returns a message identifying the applicable allowance.
Example Limit Response:
ERROR: DAILY REQUEST LIMIT REACHED - [100 PER DAY]
Endpoint Locations:
· Aircraft/getAllAircraftHistoryByAircraftID/{aircraftId}/{securityToken}
· Aircraft/getAllAircraftHistoryByAircraftIDPaged/{aircraftId}/{securityToken}/{pageSize}/{page}
· Aircraft/getAllFlightDataHistoryByAircraftID/{aircraftId}/{securityToken}
· Aircraft/getAllFlightDataHistoryByAircraftIDPaged/{aircraftId}/{securityToken}/{pageSize}/{page}
New: Airport Flight Data Endpoints
Description:
Added two new Customer API endpoints that allow authorized customers to retrieve historical flight data associated with predefined airport(s):
· getAllFlightDataHistoryByAirport
· getAllFlightDataHistoryByAirportPaged
Access is managed according to the customer’s API subscription. The authorized airport(s) are configured and maintained by JETNET. Customers may apply timeframe, airframe, make, and model filters to narrow their results, but requests will only return flight data associated with their authorized airport.
The endpoints have a default allowance of 100 calls per day. Custom daily limits may be configured based on the customer’s subscription.
Paged and non-paged requests share the same daily allowance. Retrieving additional pages from the same request does not count as an additional API call, ensuring that a multi-page response can be completed after the initial request is accepted.
Daily request limits reset at midnight Eastern Time. If a customer reaches the daily limit, the API returns a message identifying the applicable allowance.
If an airport has not been configured for the subscription, the API will not return flight data.
Example Limit Response:
ERROR: DAILY REQUEST LIMIT REACHED - [100 PER DAY]
Example Airport Configuration Response:
ERROR: NO AIRPORTS CONFIGURED FOR SUBSCRIPTION
Endpoint Locations:
· Aircraft/getAllFlightDataHistoryByAirport/{securityToken}
· Aircraft/getAllFlightDataHistoryByAirportPaged/{securityToken}/{pageSize}/{page}
Update: Airport Flight Data Endpoints
Description:
Country names returned in Customer API responses now use consistent title case formatting. Values previously displayed in all capital letters, such as CANADA, BRAZIL, and PAKISTAN, are now returned as Canada, Brazil, and Pakistan.
The update applies across Customer API endpoints that return country information while preserving abbreviations such as U.S. Existing correctly formatted values remain unchanged.
Update: Expanded Operator and Contact Information
Description:
The getFlightdata and getFlightdataPaged endpoints now return additional operator company and primary contact information. New fields include operator phone numbers, business type, email address, alternate name, parent company ID, and contact details.
Important Breaking Change
The existing operator_state field now returns the full state name instead of the state abbreviation.
Previous response: "operator_state": "NY"
New response: "operator_state": "New York"
The state abbreviation is now returned in the new operator_stateabbr field:
"operator_stateabbr": "NY"
Customers using mappings or integrations that expect operator_state to contain a two-character abbreviation must update them to use operator_stateabbr.