WeatherAPI · Rate Limits

Weatherapi Rate Limits

WeatherAPI.com enforces a monthly call-volume quota (the plan entitlement: 100K → 10M+) as its primary control. Per-second request limits are not published as numeric values on the public pricing or docs pages — the provider says "very high concurrency, contact us if you need a specific number." The Business and Enterprise tiers add IP allow/block lists. Quota is scoped to the account (API key); exceeding it returns HTTP 403 with a JSON ErrorResponse explaining "API key has exceeded calls per month quota." Hard infrastructure throttling responds with HTTP 429.

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

It captures 7 rate-limit definitions, measuring requests_per_month, requests_per_second, and locations_per_request.

The profile also includes 6 backoff/retry policies defined and response codes documented for quotaExceeded, throttled, invalidKey, and badRequest.

Tagged areas include Rate Limiting, Weather, and Geolocation.

7 Limits Throttle: 429 Quota: 403
Rate LimitingWeatherGeolocation

Limits

Monthly call quota (Free) account
requests_per_month · month
100000
Resets on the calendar month boundary. Excess returns HTTP 403.
Monthly call quota (Starter) account
requests_per_month · month
3000000
Monthly call quota (Pro+) account
requests_per_month · month
5000000
Monthly call quota (Business) account
requests_per_month · month
10000000
Monthly call quota (Enterprise) account
requests_per_month
-1
Custom quota negotiated per contract.
Burst / per-second throttle account
requests_per_second
not publicly documented — contact support for guaranteed concurrency
Hard throttling returns HTTP 429; the SLA targets 99–100% availability with 200ms average response time.
Bulk request size (Pro+ and above) account
locations_per_request
50
POST /current.json#bulk accepts up to 50 location entries per call.

Policies

Quota scope
All quotas are scoped to a single API key (account). Multiple keys can be issued from the same account dashboard.
Quota reset
Monthly quotas reset at 00:00 UTC on the first day of the calendar month.
Error semantics
- 400 — malformed request (missing q, invalid date format, invalid days range). - 401 — missing or unrecognised API key. - 403 — recognised key, but plan does not permit the requested endpoint, parameter, or quota is exhausted. - 429 — infrastructure throttling; retry with exponential backoff.
Retry guidance
On 429 or transient 5xx, retry with exponential backoff (e.g. 1s, 2s, 4s, 8s) up to 5 attempts. The 200ms average response time means jitter of ±50ms is appropriate.
Geographic restriction
Forecast and history endpoints are global; sports data is currently football (soccer), cricket, and golf. IP lookup respects EU privacy where required.
SLA
- Free 95.5% - Starter / Pro+ 99% - Business 99.9% - Enterprise 100% with contractual SLA

Sources