Terms

Service use and source data rights.

Using CleAPI

Use the APIs and tools only for purposes you are authorized to perform. Keep your credentials secure. Do not bypass access controls or limits, probe private destinations, or submit content you lack permission to share.

Source data

Source licenses govern reuse of the data. API access limits apply to CleAPI's hosted service; they do not change ownership or reuse rights in the underlying datasets.

Airports · OurAirports

Airport data from OurAirports. OurAirports dedicates its data to the public domain. CleAPI normalizes and indexes fields while retaining source IDs; invalid optional website and Wikipedia URLs are omitted and counted in metadata.

OurAirports data terms

Places · GeoNames

Contains GeoNames data, licensed under Creative Commons Attribution 4.0. CleAPI uses cities500 and reference files, normalizes fields, and retains source IDs and aliases. Preserve appropriate credit, the license link and the notice of changes when reusing the data. Do not imply source endorsement or impose restrictions that conflict with the license.

GeoNames CC BY 4.0

Coverage and availability

Data is supplied as-is, without a guarantee of accuracy, timeliness, completeness or suitability for your use. Places covers cities500, not every geographic feature. Airport data is not certified for navigation. Check each response's source, coverage, release and quality metadata. Daily refresh is a target, not a guarantee; no service availability commitment is offered here.

Allowances and payment

Enabled accounts have configured monthly allowances and minute limits. Successful responses count toward the allowance; requests stop when it is exhausted. Automatic overage billing is not enabled. Commercial prices and checkout are not configured. Any future service fee covers hosting, ingestion, updates and API processing, rather than ownership of the source data.

Pricing status

Temporary webhook history

The receiver is a temporary debugging inbox. Events stop appearing after one hour and may be evicted sooner. Legacy endpoint IDs permit shared history access; account-owned endpoints require the owning account to read history. Keep your own records when persistence matters and use synthetic payloads.

Read the privacy information or contact CleAPI.