Tomorrow.io · Rate Limits

Tomorrow Rate Limits

Tomorrow.io enforces per-API-key rate limits across three time windows: requests per second, requests per hour, and requests per day. Free keys are capped at roughly 3 RPS / 25 RPH / 500 RPD; paid tiers scale these limits up per the subscription. Map tile requests count against the same quota as Timelines/Realtime/Historical/Routes calls. Limits apply per-key, not per-account, so high-volume integrations should request multiple keys or upgrade to Enterprise for custom raised limits.

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

It captures 6 rate-limit definitions, measuring requests_per_second, requests_per_minute, and varies.

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

Tagged areas include Rate Limiting, Weather, Forecast, and Climate.

6 Limits Throttle: 429 Quota: 429
Rate LimitingWeatherForecastClimate

Limits

Free tier — requests per second key
requests_per_second · second
3
Burst limit on the Free plan.
Free tier — requests per hour key
requests_per_minute · hour
25
Hourly cap on the Free plan.
Free tier — requests per day key
requests_per_minute · day
500
Daily cap on the Free plan.
Hobby tier — requests per day key
requests_per_minute
see Hobby plan quota
Higher daily quota than Free; per-second and per-hour limits scale accordingly.
Builder tier — requests per day key
requests_per_minute
see Builder plan quota
Production-grade daily quota; per-second / per-hour limits scale.
Enterprise — custom account
varies
custom — negotiated per contract
Raised limits, custom concurrency, dedicated infrastructure available.

Policies

Per-key scoping
Limits apply per API key. Issue multiple keys across services to parallelise quota; do not share a single key across production tenants.
429 with Retry-After
On throttle the API returns HTTP 429 and a Retry-After header (seconds). Clients must back off and retry no sooner than the indicated delay.
Exponential backoff
Recommended client policy is exponential backoff with jitter on 429 / 503 — start at the Retry-After value and double on consecutive throttles.
Idempotent reads
Realtime, Forecast, Timelines, Historical, Climate Normals, Routes, and Map Tiles are all idempotent — retries are safe and recommended after backoff.
Map tiles count
Each `/map/tile/{z}/{x}/{y}/{field}/{time}` request consumes one quota slot. Cache tiles aggressively on the client side.
Raise via support
Builder and Enterprise customers can request raised per-second or daily quotas via account management; raises are not self-service.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/tomorrow-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.