Tibber · Rate Limits
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.
2 Limits
Throttle: 429
EnergyRate LimitingOAuth
Limits
per personal access token
Rate limits are enforced but not numerically disclosed. Excessive polling of `liveMeasurement` from a single token results in disconnection; use the websocket subscription rather than repeatedly polling the query API.
per OAuth client + per access token + per endpoint
Tibber documents 429 throttling with `Retry-After` plus 5xx infrastructure retry windows. Treat the API as rate-limited even when 429s are rare; if observed latency climbs, proactively reduce poll frequency.