AIRCONCOURSE: Concourse
An airport concourse with terminal association, gates, airlines served, and dining facilities.
Default definition. This article describes the default
AIRCONCOURSE 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 AIRCONCOURSE.Entity properties
| Property | Value |
|---|---|
| Entity code | AIRCONCOURSE |
| Display name | Concourse |
| Plural | Concourses |
| Level | 30000 |
Use cases
Aviation entity for airport concourses. Single-column layout with a form section (name, airport IATA, terminal name, gates, airlines) followed by a relatedlist of AIRREST dining facilities via comboKeyEntity relationship. Child of AIRTERMINAL and grandchild of AIRHI. AI disabled (ai: false). The 'list' property appears after the definition array rather than before it. Provides the most granular level of airport infrastructure mapping.
Fields
General: Concourse information
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
airport_iata | text | Yes | Airport IATA Code. |
terminalName | text | Yes | Terminal name. |
gates | text | Yes | Gates. |
airlines | text | Yes | Airlines. |
Relationships
- Related lists:
AIRREST.
Creating a Concourse via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "AIRCONCOURSE",
"level": 30000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Name",
"airport_iata": "Airport IATA Code",
"terminalName": "Terminal name",
"gates": "Gates"
}Listing Concourses records
GET /v1/entities/AIRCONCOURSE/SUB