Reference API

The permit requirements, lead times and airport data behind our own tools, as JSON. Built for flight-planning software, dispatch systems and AI agents that need to know what a routing through the Middle East or North Africa actually requires.

Why this exists

Global flight-planning tools are thin on this region. We file these permits every day, so the requirements, lead times and document lists come from operational practice rather than a scraped table. Free and open at this tier, no key. Rate limits and keys arrive with the commercial tier.

Endpoints

Base URL

GET/countries

Every country we cover, with overflight and landing lead times in working days and permit validity.

GET/permits?countries=IQ,EG&type=cargo&permit=ldg

Requirements for a routing. Returns per-country lead time, validity and the exact document set — which differs by flight type and by whether you are overflying or landing.

countries: required — comma-separated ISO codes
permit: ovf · ldg · both (default both)
type: passenger · cargo · ambulance · ferry · private · humanitarian

GET/airports/{icao}

Airport reference record by ICAO or IATA code, from a 5,000-airport dataset.

GET/openapi.json

Machine-readable specification, so agents and code generators can consume the API directly.

Notes

CORS is open, so you can call this straight from a browser.
Responses cache for one hour.
Bad input returns 422 with an explanation, not 404.
This is planning reference data. Authorities change requirements without notice — confirm with our desk before filing.

Need higher limits, a service-level agreement, or fields we do not publish here (fee bands, station contacts, historical approval times)? Talk to us about the commercial tier →