1KEY Developers
Guides

Rate limits

Rate limits

Limits apply per API key.

Limit Value
Requests 50 per second, bursts up to 100
Streams and waits open at once (/events/stream, /requests/stream, wait on event lists) 10 per key, 50 per organization
Streams and waits opened 30 a minute per key

A stream or wait counts as open until it ends; close one you no longer read before opening another.

The developer portal reads these streams too, for its live pages. Acting as you (not one of your keys), it counts against you rather than a key, and against a pool of its own rather than your organization's 50, so open portal tabs never take your integrations' slots:

Portal limit Value
Streams open at once 20 per signed-in person, 100 per organization
Streams opened 60 a minute per signed-in person

When you choose one of your keys to act with in the portal, its streams count against that key, as they would from your code.

Every response carries the remaining budget:

RateLimit-Limit: 50
RateLimit-Remaining: 47
RateLimit-Reset: 1

Past a limit, requests get 429 rate_limited; past the request rate, with a Retry-After header in seconds. Wait that long, then retry. If you keep hitting limits, spread requests out or use separate keys for separate jobs.