# Flight API

> Query any past flight by number and date. Actual departure and arrival times, block time, aircraft and delay minutes — one REST endpoint, one settled record.

One authenticated GET takes a flight number and a UTC date and returns a single settled record: actual and scheduled times on both ends, aircraft, carrier and arrival delay in minutes. All timestamps are UTC. Keys are prefixed `flt_` and sent as `Authorization: Bearer` or `x-api-key`.

A paid plan is required: an account with no active subscription is refused with `402`. One credit is taken per authorised request, before the resolve runs, and the remaining balance is returned in the `X-Credits-Remaining` header.

## Machine-readable

- [OpenAPI 3.1 specification](https://flight-api.dev/openapi.json): every endpoint, parameter, schema and status code
- [Full reference as JSON](https://flight-api.dev/api/docs): the same content as structured data, plus examples
- [Full reference as Markdown](https://flight-api.dev/docs.md): one document, readable start to finish

## Endpoints

- `GET https://flight-api.dev/api/v1/flights/status`: Resolves one flight on one date and returns the selected record. Settled disruptions are replayed from storage.
- `GET https://flight-api.dev/api/v1/account`: Returns the account and key behind the supplied credential, its lifetime request count and the credit position for the current window. Unmetered — this call costs nothing.
- `GET https://flight-api.dev/api/health`: Unauthenticated. Returns immediately.

## Docs

- [API reference](https://flight-api.dev/docs): rendered documentation
- [Coverage and limits](https://flight-api.dev/coverage): what is queryable and what is never stored
- [Pricing](https://flight-api.dev/pricing): request allowances and overage rates
- [Terms of service](https://flight-api.dev/terms): licence, acceptable use, billing
- [Privacy policy](https://flight-api.dev/privacy): account data, keys, processors