GET /
Returns the machine-readable documentation this page is rendered from. Free, and everything an agent needs.

byAPI3FreeAirnode v0.1.2
AeroDataBox is an aviation data API covering live and historical flight status, airport schedules, airport and runway reference data, and aircraft records. This Airnode wraps its read endpoints, so a consumer receives a flight's status with a signature saying this Airnode obtained it from AeroDataBox at this time, rather than trusting a copy that passed through an unnamed hop.
Whether a flight is late is a question whose answer changes by the minute, which makes it worth asking an Airnode: the attestation dates the answer as well as attributing it. Live status and estimated times only exist for airports AeroDataBox tracks, so airportFeedStatus is where to check before concluding a flight has no data.
AeroDataBox is reached through RapidAPI and the plan behind it is metered in units, with the more expensive endpoints costing many times a cheap one. The operations here are the ones that cost the least, so airport delay statistics, route statistics and flight alert webhooks are not served.
Every response carries an EIP-191 signature from the Airnode that served it, so the data can be attributed back to its source rather than trusted on reputation.
Ask the Hub what AeroDataBox can tell you →Served at https://airnode-aerodatabox.fly.dev/. Each operation is reached the way the provider documents it, under https://airnode-aerodatabox.fly.dev/api, and answers with the provider's own response and the attestation in headers, so a client built against the provider works unchanged. The same operations are also served as one JSON envelope on POST /, which the HTTP interface covers. Every request below can be sent from this page, and what comes back is verified right here in the browser.
Returns the machine-readable documentation this page is rendered from. Free, and everything an agent needs.
The provider's own requests, one per operation, forwarded as they are. The provider's response comes back untouched, with the attestation in the X-Airnode headers.
Paste a response to verify it originates from the current Airnode: the JSON a POST / answers with, or a passthrough response with its headers, as curl --include prints it.