Tibber Rate Limits
Tibber publishes rate-limit guidance but not specific per-token or per-client numeric ceilings. Both the legacy GraphQL API and the modern Data API are positioned as rate-limited services; clients must implement retry with exponential backoff plus jitter, and respect the `Retry-After` header.
Tibber Rate Limits is the machine-readable rate-limit profile for Tibber on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions.
The profile also includes response codes documented for throttled and serverBusy.
Tagged areas include Energy, Rate Limiting, and OAuth.
Limits
Sources
- https://data-api.tibber.com/docs/api-usage/rate-limiting/
- https://data-api.tibber.com/docs/api-usage/retry-backoff/
- https://developer.tibber.com/docs/guides/calling-api
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/tibber-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.