Credits and rate limits
How API usage consumes subscription credits and rate limits.
Credits
The Developer API uses the API credits included in your NaijaRadar subscription. There is no separate developer balance.
- A successful flight search with at least one result costs 1 credit.
- A successful flight detail lookup costs 1 credit.
GET /v1/meis free.- Empty search results, validation errors, authentication errors, and upstream failures do not cost credits.
Quota fields are included in every response and in response headers:
| Header | Meaning |
|---|---|
X-Credits-Limit | Total credits available on your current plan |
X-Credits-Used | Credits used in the current billing period |
X-Credits-Remaining | Credits remaining |
When the allowance is exhausted, flight data requests return HTTP 402.
Rate limits
Each active API key is limited to 60 requests per minute by default. Your deployment can change this value.
Every response includes:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Requests allowed in the current window |
X-RateLimit-Remaining | Requests remaining in the window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Retry-After | Seconds to wait when a 429 is returned |
Rate limits are applied per API key, while credits are shared across the account's subscription.