Pulling Core JETNET IDs for Use in Your API Workflows

The JETNET API uses stable internal identifiers — such as aircraftid, modelid, companyid, and contactid — to connect data across different endpoints. These IDs are essential when you're building integrations, filtering data, or normalizing records within your own systems.

You’ll need these identifiers to:

• Match aircraft, company, or contact records to your internal database
• Use the IDs in downstream API calls
• Structure your data for integration using JETNET IDs

This guide outlines the primary methods for retrieving these IDs — whether you’re building a lightweight reference table or a full data sync pipeline.

Option 1: Use getAircraftList (for Aircraft-Only Info)

The getAircraftList endpoint provides basic aircraft data — including fields like aircraftid, modelid, make, and model.

• The response includes a consistent set of fields for each aircraft record.
• You can apply filters such as lifecycle: InOperation or forsale: true to limit the dataset.
• If you're retrieving a large dataset, be prepared to handle and process tens to hundreds of thousands of records in a single response.

If you prefer to work with a subset of fields, you can process the full response into a custom table using whatever tools best fit your environment — Python, JavaScript, Excel, etc.

Option 2: Use getBulkAircraftExport (for Rich, Normalized Data)

getBulkAircraftExport includes all the core aircraft identifiers and descriptive fields you’ll find in getAircraftList, along with a significantly expanded dataset. This includes associated company and contact records, phone numbers, ownership relationships, and company/contact-related aircraft events — all returned in a single response.

If you're working with large data volumes, a paginated version of this endpoint — getBulkAircraftExportPaged — is also available. 

Summary Comparison

Technical Feature Comparison

Both endpoints provide the JETNET IDs you'll need to join records, enable integrations, and normalize aircraft-related data across systems.