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, in the API Commons Rate Limits shape.

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

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 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 Exhausted: HTTP 429
Method: generated, dated 2026-07-03.
Written by API Evangelist on 2026-07-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

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/sensibo-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.