Sensibo · Rate Limits

Sensibo Rate Limits

Sensibo rate limits the API but does not publish a fixed numeric request cap. When a client exceeds the limit the API returns HTTP 429. Sensibo's guidance is that sending an `Accept-Encoding: gzip` header raises the effective limit, which implies limiting is influenced by response payload volume as well as request count - so clients should request only the fields they need (via the `fields` parameter) and accept gzip. Historical measurements are capped at seven days per request regardless of rate. Practical integrations poll measurements on the order of tens of seconds to a few minutes rather than continuously, since Sensibo devices report to the cloud on an interval and there is no push/streaming API to subscribe to.

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

It captures 3 rate-limit definitions, measuring requests and days.

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

Tagged areas include Smart Home, IoT, Air Conditioning, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Smart HomeIoTAir ConditioningRate LimitingQuotas

Limits

API Requests account
requests
not published
A 429 indicates the rate limit was exceeded. No fixed numeric cap is documented.
Gzip Allowance account
requests
raised with gzip
Sending an Accept-Encoding gzip header increases the effective rate limit.
Historical Window request
days
7
historicalMeasurements returns at most seven days of data per request.

Policies

Backoff Strategy
On a 429, back off exponentially with jitter and retry rather than hammering the endpoint.
Response Minimization
Use the fields query parameter and gzip compression to reduce payload size and stay within limits.
Sensible Polling
Poll measurements on an interval (tens of seconds to minutes); there is no push or streaming API to subscribe to.

Sources