Primary IDs used in the JETNET API
These are the core IDs used across the JETNET API. Each ID represents a specific internal record — such as an aircraft, company, or contact — and is commonly required when filtering results or requesting detailed data. This guide will help you understand where each ID comes from and which API endpoints accept them.
Whether you're syncing data into a CRM, pulling update deltas, or building custom workflows, this reference is your key to knowing which IDs to use where.
Core IDs
| Field | Description |
|---|---|
aircraftid / acid |
Unique aircraft identifier |
modelid |
Aircraft model identifier |
companyid |
Unique company identifier for owning/operator companies |
contactid |
Unique contact identifier for individuals associated with aircraft or companies |
Key Notes:
Normalize IDs to avoid duplicates.
Relationships are hierarchical: multiple companies per aircraft, multiple contacts per company.
Use numeric IDs consistently for linking records.
Core IDs in Endpoints
| Field | Returned by | Where It’s Used |
|---|---|---|
|
/api/Aircraft/
/api/Company/
|
Used in: All /api/Aircraft/Accepted as array: /api/Company/Accepted as single value or array:
|
|
/api/Company/
/api/Aircraft/
/api/Events/
|
Used in: All /api/Company/Accepted as single value or array:
/api/Aircraft/Accepted as single value: |
|
/api/Company/
/api/Aircraft/
/api/Events/
|
Used in: All /api/Company/Accepted as single value or array: /api/Aircraft/Accepted as single value or array: /api/Events/Accepted as single value or array: |
|
/api/Utility/
|
Used in: All endpoints that return or filter by aircraft model View in Swagger Accepted as filter value: Aircraft/getBulkAircraftExportAircraft/getCondensedOwnerOperatorsAircraft/getCondensedOwnerOperatorsPaged
|