Rate limits are scoped to the workspace, not to the token, and are configured per plan in the workspace settings. A workspace with three tokens still has one shared quota.
Headers
Every response carries:
X-RateLimit-Limit— total requests in the current window.X-RateLimit-Remaining— requests left in the current window.X-RateLimit-Reset— Unix timestamp when the window resets.
When you hit the limit, the response is 429 Too Many Requests and
includes an extra header:
Retry-After— seconds to wait before the next request will be accepted.
Bulk endpoints
Some endpoints cost more than one request against your quota:
POST /v1/moments/bulkwithids: [...]of lengthNconsumesNunits.DELETE /v1/moments/bulkwithids: [...]of lengthNconsumesNunits.
There is no per-endpoint "cost" header; you find out you over-spent
by hitting the 429. The recommended pattern is to send batches of
≤50 IDs and respect the Retry-After header on the 429.
When the limit is exceeded
The API returns 429 Too Many Requests and includes Retry-After with
the number of seconds to wait before retrying.
