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, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions.
Limit state is signalled in the retryAfter response header, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes response codes documented for throttled and serverBusy.
Tagged areas include Energy, Rate Limiting, and OAuth.
retryAfter
generated, dated 2026-05-25.
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.