Govee · Rate Limits

Govee Rate Limits

The Govee Developer API enforces an account-wide limit of 10,000 requests per API key per day (rolling 24 hours). In addition, a per-device per-minute limit applies to control and query calls so that a single device is not flooded with commands (community-observed at roughly 10 requests per device per minute). Rate-limit state is exposed on responses via API-RateLimit-Limit, API-RateLimit-Remaining, and API-RateLimit-Reset headers, and exceeding a limit returns HTTP 429. The local LAN API is not subject to the cloud rate limits.

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

It captures 3 rate-limit definitions, measuring requests.

Limit state is signalled in the API-RateLimit-Limit, API-RateLimit-Remaining, and API-RateLimit-Reset response headers, and 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 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Smart Home, Smart Lighting, IoT, Device Control, and Rate Limiting.

3 Limits Exhausted: HTTP 429 API-RateLimit-LimitAPI-RateLimit-RemainingAPI-RateLimit-Reset
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 HomeSmart LightingIoTDevice ControlRate LimitingQuotas

Limits

Account Daily Requests account
requests
10000 per day
Per API key, rolling 24 hours. Exceeding returns HTTP 429.
Per-Device Request Rate device
requests
per-device per-minute (approx 10/min, integrator-reported)
Protects individual devices from command flooding on control and state calls.
LAN API local-network
requests
not cloud-limited
Local UDP control bypasses the cloud rate limits entirely.

Policies

Backoff on 429
On HTTP 429, stop sending and retry with exponential backoff, guided by the API-RateLimit-Reset header.
Prefer State Caching
Cache device state and avoid polling tighter than needed; the daily cap is shared across all calls on the key.
Use LAN for High Frequency
For rapid or high-frequency control (e.g. animations), use the local LAN API, which is not bounded by the cloud limits.
Event Subscription over Polling
For capabilities that emit events, subscribe over MQTT (topic GA/{apiKey}) instead of polling /device/state to conserve the daily quota.

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