Never use extra accounts, extra API keys, bots, proxies, rotating IPs, or automation patterns to bypass limits. Bypass attempts may lead to limited, suspended, or revoked keys.
Plan limits
| Plan | API keys | Premium keys | Daily requests | Pacing |
|---|---|---|---|---|
| Premium | 10 | 10 | 2,500 | 1 request per second |
Staff-issued support keys and approved partner overrides may have custom limits. The response headers are the source of truth for your active quota.
Headers
Dock sends standard rate-limit headers on authenticated API requests.Current short-window pacing limit.
Remaining requests in the short-window bucket.
Time when the short-window bucket resets.
Daily request limit for the authenticated key.
Remaining requests in the daily bucket.
Present on
429 responses. Wait at least this many seconds before retrying.Verification-session limits
Verification sessions have extra guardrails because clients often poll for completion.| Limit | Value |
|---|---|
| Session lifetime | 5 minutes |
| Create-session burst | 6 sessions |
| Create-session refill | 1 session every 10 seconds |
| Minimum poll interval | 2 seconds |
| Long-poll wait max | 25 seconds |
| SSE stream max | 30 seconds |
| Premium poll limit | 150 polls per session |
Handling 429 responses
Acceptable use
Do not:- Use multiple keys, accounts, bots, proxies, or rotating IPs to avoid limits.
- Scrape, automate, or repeatedly call endpoints in a way intended to bypass quotas or access controls.
- Continue retrying aggressively after
429responses. - Share API keys with untrusted parties.
- Disrupt, overload, reverse engineer, resell, or sublicense Dock services.