AIRTERMINAL: Terminal
An airport terminal with IATA code, coordinates, passenger count, and related concourses/dining.
Default definition. This article describes the default
AIRTERMINAL 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 AIRTERMINAL.Entity properties
| Property | Value |
|---|---|
| Entity code | AIRTERMINAL |
| Display name | Terminal |
| Plural | Terminals |
| Level | 250 |
Use cases
Aviation entity for airport terminals. Two-column layout: left column has terminal name, airport IATA code, lat/lon, and annual passenger count; right column has relatedlists for AIRCONCOURSE and AIRREST (dining facilities), both using comboKeyEntity relationships. AI-enabled. Child of AIRHI via comboKey. Serves as an intermediate level in the airport hierarchy between AIRHI and AIRCONCOURSE.
Fields
General: Concourse information
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Terminal name. |
airport_iata | text | Yes | Airport IATA Code. |
lat | number | Latitude. | |
lon | number | Longitude. | |
passengers | number | Annual passenger count. |
Relationships
- Related lists:
AIRCONCOURSE,AIRREST.
Creating a Terminal via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "AIRTERMINAL",
"level": 250,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Terminal name",
"airport_iata": "Airport IATA Code",
"lat": 0,
"lon": 0
}Listing Terminals records
GET /v1/entities/AIRTERMINAL/SUB