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, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests.

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 Throttle: 429
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