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, North Africa and the surrounding corridors actually requires.
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 for fair use, no key. Rate limits apply, and these terms may change.
Base URL
Every country we cover, with overflight and landing lead times in working days and permit validity. A lead time is null where our desk confirms the requirement with each request.
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.
ovf · ldg · both (default both)passenger · cargo · ambulance · ferry · private · humanitarian (default passenger)For permit=both the longer of the two lead times applies. Countries without published data come back with leadDaysWorking: null and requirementsOnRequest: true: our desk confirms their lead time and documents with each request.
Airport reference record by ICAO or IATA code, from a 5,000-airport dataset.
Machine-readable specification, so agents and code generators can consume the API directly.
Questions about the API, or need a field we do not publish here? Ask our desk →