Airports
Public domainSearch facility names and codes, look up an airport or find nearby facilities by coordinate. IATA, source ICAO, GPS and local codes stay separate.
OurAirports covers airports, heliports and other facilities. Closed facilities are excluded by default. Source values can be missing or inaccurate; airport records are not certified for navigation.
Places
CC BY 4.0Search settlement names and aliases, filter by country and look up a place. Original GeoNames IDs and administrative reference codes are retained.
The cities500 collection covers populated places over 500 inhabitants and administrative seats through PPLA4. It does not include every geographic feature, street or address.
Know what came back.
Source rights
OurAirports data is public domain. GeoNames data retains its CC BY 4.0 attribution and reuse rights. CleAPI normalizes and indexes the records; hosted service limits do not change the data license.
Release metadata
Search and record responses include source details, coverage, release identity, dates and quality warnings. Pin release_id to keep list pages on one snapshot. Daily refresh is a target; check actual response dates.
Clear limits
Lists default to 20 records and return at most 100. Enabled accounts share a configured UTC monthly allowance across keys. Successful calls count toward it; requests stop at the limit, with automatic overage charges disabled.
Read the API contract and usage guide →Beyond the catalog
An API around your workflow.
Talk to CleAPI about a custom API, data conversion, integration between existing systems or work around legacy software. Scope the input, output and access needs before choosing an implementation.
Discuss a project ↗Everyday developer tools
Format JSON, convert CSV, inspect tokens, build requests and debug webhooks. The tool catalog keeps these small tasks close to the data APIs.
Browse tools →A scoped project, from first question to maintenance.
- 01
Consultation
Understand the data, systems and workflow.
- 02
Design
Agree on the API contract and boundaries.
- 03
Development
Connect systems and transform data.
- 04
Testing
Check the intended workflows and failure cases.
- 05
Deployment
Plan access, hosting and the rollout.
- 06
Support
Define the ongoing maintenance needs.
Project scope, hosting, deployment and support terms are agreed for each engagement.