Airport Gap · Rate Limits

Airport Gap Rate Limits

Airport Gap enforces a single rate limit of 100 requests per minute tracked by IP address, applied uniformly across all endpoints (public and authenticated). Exceeding the limit returns HTTP 429 Too Many Requests. The window resets every 60 seconds. There are no per-key, per-day, or monthly quota caps; the only throttle is the per-IP per-minute ceiling.

Airport Gap Rate Limits is the machine-readable rate-limit profile for Airport Gap on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 1 rate-limit definition, measuring requests_per_minute.

The profile also includes 4 backoff/retry policies defined and response codes documented for rateLimitExceeded, unauthorized, notFound, and validationError.

Tagged areas include Rate Limiting, Airports, and Aviation.

1 Limits
Rate LimitingAirportsAviation

Limits

Requests per minute (per IP) ip
requests_per_minute · minute
100
Applied to all endpoints regardless of authentication status. Tracked by the caller's IP address. Resets every 60 seconds. Exceeding the limit returns HTTP 429.

Policies

IP-based tracking
Rate limit counters are keyed to the caller's IP address. All 10 Airport Gap endpoints share the same counter; there is no per-endpoint or per-token differentiation.
Per-minute window reset
The 100-request counter resets every minute. There is no concept of a daily or monthly quota.
429 on limit breach
When the limit is exceeded the API responds with HTTP 429 Too Many Requests. Callers should implement exponential backoff and wait for the next minute window before retrying.
No authenticated-vs-public split
Authenticated requests (Bearer token) and unauthenticated requests share the same per-IP limit. Token ownership does not grant a higher rate limit.

Sources