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.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/sensibo-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.