Cities Model
A city belongs to a country and can be associated with an administrator and dropdown options. See the operation guide for complete operation schemas; this guide summarizes shared concepts.
Operations
| Action | Method | Resource |
|---|---|---|
| List | GET | /countries/{country}/cities |
| Find | GET | /countries/{country}/cities/{city} |
| Create | POST | /countries/{country}/cities |
| Update | PUT | /countries/{country}/cities/{city} |
| Delete | DELETE | /countries/{country}/cities/{city} |
Shared concepts
nameis required when a city is created and can be used in supported filters.country_ididentifies the parent country. For create and update requests,country_idcomes from the route parameter before validation.administrator_idcan associate a user with the city and may benull.enabledcontrols the city's status.country,administrator, andoptionsare relationships that list and find requests can expand throughparams.
The city operations described here are limited to role levels 0 and 1; do not assume broader access. Field presence varies by operation and requested relations, so this is not a complete response schema.