Skip to content
CleAPI

The CleAPI catalog

Explore the data.

Airport codes, city names and coordinates. Find the dataset you need, check its coverage, then make a request with one CleAPI key.

Try a request

2 datasets

Airports

OurAirports

Resolve airport codes, find a facility by name, or discover airports around a coordinate.

iataCodeicaoCodelatitudelongitude

Coverage and reuse

Airports, heliports and other facilities in OurAirports. Closed facilities are excluded by default.

IATA, ICAO, GPS and local codes remain separate; missing codes stay null. Use as reference data and validate information for operational decisions.

Public domain

Endpoints

  • GET/api/v1/airports

    Search names and codes. Filter by country or facility type.

  • GET/api/v1/airports/{id}

    Look up a facility. Use an oa: ID returned by search.

  • GET/api/v1/airports/nearby

    Find nearby facilities. Search by latitude, longitude and radius.

Example requests

GET /api/v1/airports?iata=SFO&country=US
GET /api/v1/airports/nearby?latitude=37.6213&longitude=-122.379&radius_km=50

Build airport selectors, destination references and facility discovery for a map. Examples show request syntax, not a live response.

Read full parameter docsOpen explorer

Find cities and settlements by name or alias, with coordinates, population and time zone fields.

alternateNamescountryCodepopulationtimezone

Coverage and reuse

GeoNames cities500: populated places over 500 inhabitants and administrative seats, with country and administrative references.

Coverage is the cities500 collection rather than every geographic feature or street address. Preserve GeoNames credit, the license link and notices of changes when reusing data.

CC BY 4.0

Endpoints

  • GET/api/v1/places

    Search names and aliases. Narrow results with a country code.

  • GET/api/v1/places/{id}

    Look up a settlement. Use a gn: ID returned by search.

Example requests

GET /api/v1/places?q=San%20Francisco&country=US

Build city selectors and place references that can be filtered by country. Examples show request syntax, not a live response.

Read full parameter docsOpen explorer

Shared dataset metadata

Inspect releases, import dates, source credits and normalization warnings for both collections.

GET /api/v1/metadata

Know what you're using.

Response format →

Check the import dates

Response metadata includes retrieval, source and import dates. Daily refresh is a target; those dates show the completed release.

Keep pages on one release

Use the returned release ID as release_id when paginating. Older releases let you keep the same dataset snapshot.

Keep the source attached

Metadata carries attribution, license and normalization notices. Source data is supplied as-is and can contain errors.

Requests require a valid key and an imported dataset. Account access is being configured; the explorer shows the actual response, including setup errors.

Try a request

Loading the request explorer…