Skip to main content
Dock rate limits requests to keep the API stable and fair for every integration.
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

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.
number
Current short-window pacing limit.
number
Remaining requests in the short-window bucket.
unix timestamp
Time when the short-window bucket resets.
number
Daily request limit for the authenticated key.
number
Remaining requests in the daily bucket.
seconds
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.
Prefer GET /api/v1/verify/session/:sid?wait=25 or GET /api/v1/verify/session/:sid/stream instead of polling in tight loops.

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 429 responses.
  • Share API keys with untrusted parties.
  • Disrupt, overload, reverse engineer, resell, or sublicense Dock services.
For the full policy, read the Terms of Service and Privacy Policy.