Customer API Release: 9/09/2025

New Endpoint

getAllAircraftObjects()

Retrieve Multiple Aircraft Objects in a Single Response.  

This new POST endpoint accepts multiple aircraft IDs as input and returns the corresponding aircraft objects in a single request. It provides the same functionality as getAircraft(), but supports bulk retrieval for improved efficiency.

Location: api/Aircraft/getAllAircraftObjects/{security token}/{page size}/{page}

Example

{

"aclist": [2346,12389,65123,31904,31905]

}

Updates

Link to release notes added to swagger page.  

A link to the complete JETNET Customer API release notes have been added to the header of the Swagger page.  

Location: https://customer.jetnetconnect.com/swagger/index.html

Toggle added for including “Awaiting Documentation” companies in bulk endpoints.

Affected Endpoints:

  • getBulkAircraftExport
  • getBulkAircraftExportPaged

A new parameter, showAwaitingDocsCompanies, has been added to the bulk endpoints. By default, this parameter is set to false. When enabled, it includes companies with the name “Awaiting Documentation” in the bulk endpoint results.

Example

{

"showAwaitingDocsCompanies": true

}

Additional Values Added to Bulk Endpoints.

Affected Endpoints:

  • getBulkAircraftExport
  • getBulkAircraftExportPaged

The following fields have been added to the bulk export endpoints to provide more comprehensive aircraft data:

  • "modelicao" – Model ICAO
  • "hasadsb" – ADS-B Capable (Y/N)
  • "regnbrhex " – Hex Code
  • "prevregnbrhex" – Previous Hex Code
  • "estaftt" – Estimated Airframe Time
  • "estflighthrs" – Estimated Flight Hours
  • "estcycles" – Estimated Cycles

Additional Values Added to getAirportList Endpoint.

Affected Endpoints:

  • getAirportList

The following fields have been added to the getAirportList endpoint:

  • "latitude" – Latitude
  • "longitude" – Longitude
  • "runwaylength" – Runway Length

Change to getRelationships() Endpoint.

Affected Endpoints:

  • getRelationships

We resolved an issue that caused lower-than-expected relationship counts when querying by model ID. A query condition was excluding valid relationships, which has now been corrected.

Impact 

• More complete and accurate set of relationships when searching by model ID. 
• No breaking changes, the structure of the response remains unchanged. 
• Relationship counts may be higher than before, reflecting the corrected data.

Example

{

"showHistoricalAcRefs": true,

"modlist": [278]

}


Sign up here to stay updated on new API releases.

 

Was this article helpful?

/