DemandFlow Support Centre

AIRROUTE: Air Route

ReferenceEntity Reference16/04/2026Updated 16/04/2026
An air route between two airports with airline details, flight number, and terminal information.

AIRROUTE: Air Route

An air route between two airports with airline details, flight number, and terminal information.

Default definition. This article describes the default AIRROUTE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches AIRROUTE.

Entity properties

PropertyValue
Entity codeAIRROUTE
Display nameAir Route
PluralAir Routes
Level30000

Use cases

Aviation entity for scheduled air routes. Three-column layout: basics (flight name, airline name/callsign, IATA/ICAO codes, flight number), departure (airport, timezone, IATA/ICAO codes, terminal), and arrival (airport, timezone, IATA/ICAO codes, terminal). Distinct from AIRFLIGHT which stores actual flight instances - this entity represents the scheduled route pattern. No 'list' property defined.

Fields

General: Basics

FieldTypeRequiredNotes
nametextYesFlight.
airline_nametextYesAirline Name.
airline_callsigntextAirline callsign.
airline_iatatextAirline IATA Code.
airline_icaotextAirline ICAO Code.
flight_numbertextYesFlight Number.

General: Departure

FieldTypeRequiredNotes
dep_airporttextYesDeparture Airport.
dep_timezonetextTimezone.
dep_iatatextDeparture IATA Code.
dep_icaotextDeparture ICAO Code.
dep_terminaltextDeparture Terminal.

General: Arrival

FieldTypeRequiredNotes
arr_airporttextYesArrival Airport.
arr_timezonetextArrival Timezone.
arr_iatatextArrival IATA Code.
arr_icaotextArrival ICAO Code.
arr_terminaltextArrival Terminal.

Relationships

  • No declared relationships in the default definition.

Creating a Air Route via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "AIRROUTE",
  "level":    30000,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Flight",
  "airline_name": "Airline Name",
  "flight_number": "Flight Number",
  "airline_callsign": "Airline callsign"
}

Listing Air Routes records

GET /v1/entities/AIRROUTE/SUB

See also

airrouteair routeair routesairroutes

Was this article helpful?

← Back to Knowledge Base