Eight Sleep · Rate Limits

Eight Sleep Rate Limits

Eight Sleep does NOT publish an official public API, and therefore publishes no documented rate limits. The community client API (auth-api / client-api / app-api .8slp.net) is undocumented and unsupported. Open-source clients such as pyEight self-impose conservative polling intervals - commonly device data refreshed about once per minute and user data about once every five minutes - to avoid hammering the backend. Any server-side throttling is unpublished and may change without notice. Values here are community conventions, not reconciled provider limits.

Eight Sleep Rate Limits is the machine-readable rate-limit profile for Eight Sleep on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests.

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 Sleep, IoT, Smart Home, Unofficial, and Rate Limiting.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
SleepIoTSmart HomeUnofficialRate LimitingQuotasThrottling

Limits

Device Data Polling (community convention) account
requests
~1 request per minute
pyEight recommends refreshing device data roughly once per minute.
User Data Polling (community convention) account
requests
~1 request per 5 minutes
pyEight recommends refreshing user data roughly once every five minutes.
Server-Side Throttling account
requests
undocumented
Eight Sleep does not publish backend rate limits; 401/429 handling is up to the client.

Policies

Conservative Polling
Community clients self-throttle device/user polling to avoid load and account flags.
Token Refresh
Clients refresh the OAuth2 bearer token before expiry (e.g. ~120s buffer) and retry on 401.
Backoff Strategy
Clients should back off on errors and honor any Retry-After the backend returns.

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/eight-sleep-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.