API documentation
Documentation for the FlyItalyADSB REST API and MCP server: quickstart, authentication, endpoints, fields and units, limits and errors, history, commercial use.
Everything you need to use the API and the MCP server. For a quick question, check the FAQ.
Quickstart From a free key to your first FlyItalyADSB API response in two minutes, with curl, Python and JavaScript. Authentication An API key in X-Api-Key, OAuth for AI assistants, and agent registration with auth.md: how to get and manage access to the FlyItalyADSB API. Endpoints Every endpoint of the FlyItalyADSB REST API v2: one aircraft by ICAO hex, callsign or registration, aircraft within a radius, military, PIA, LADD and history. Fields and units The fields of an aircraft in the FlyItalyADSB API (readsb aircraft.json format) and their units: altitude in feet or "ground", speed in knots, dbFlags, seen_pos, position source. Limits and errors FlyItalyADSB API limits per plan (requests per minute, per month, radius), how they are counted, the X-FIA-* headers, and what to do about 400, 401, 403, 404, 429 and Cloudflare blocks. History FlyItalyADSB ADS-B history through the API: the dates with a track for one aircraft and one day's track, coverage since 2022, and what is not available. MCP server FlyItalyADSB's MCP server at flyitalyadsb.com/mcp: the four tools, how to connect it to Claude, Claude Code and other clients, and how requests are counted. Commercial use Using the FlyItalyADSB API in apps and devices you sell: one key per product, caching on your server, sizing the plan, CC BY-SA 4.0 attribution and when an enterprise agreement is needed. Changelog What's new in the FlyItalyADSB API and MCP server, by date.