AIRCITY: City
A city with IATA code, country, coordinates, timezone, population, type, and airport associations.
Default definition. This article describes the default
AIRCITY 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 AIRCITY.Entity properties
| Property | Value |
|---|---|
| Entity code | AIRCITY |
| Display name | City |
| Plural | Cities |
| Level | 30000 |
Use cases
Aviation reference entity for cities. Uses flat definition array with map/grid viewOptions. Fields cover identification (name, IATA code, city ID), geography (country ISO2, country objectLookup to COUNTRY, geoname ID, lat/lon in two formats, timezone, GMT offset, elevation, region), demographics (population, city type via indexedSelect), and aviation links (has_airport checkbox, primary_airport objectLookup to AIRHI, is_tourist_destination checkbox). Supports data import. Provides the city-level geographic context for airport and route data.
Fields
No form fields defined in the default layout. This entity uses non-form panels only.
Relationships
- Lookups:
countrypoints at aCOUNTRYrecord;primary_airportpoints at aAIRHIrecord.
Creating a City via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "AIRCITY",
"level": 30000,
"comboKey": "SUB:<your-sub-id>|ENT:"
}Listing Cities records
GET /v1/entities/AIRCITY/SUB