RATE_LIMITED: slow down
A 429 response with RATE_LIMITED means requests are arriving too quickly. Respect Retry-After when present, reduce concurrent requests, and use bounded backoff. Do not retry every failed request immediately. Request limits and screenshot balances are separate.
QUOTA_EXCEEDED: check available captures
Check the organization’s usage and credit balance in the dashboard. A top-up or a plan change may be needed. Waiting for a short retry interval does not replenish a used-up capture allowance. Confirm that the request uses a key from the organization whose balance you checked.
SERVICE_BUSY: retry later
A 503 with SERVICE_BUSY indicates capture workers are busy. Retry after the indicated delay with a bounded retry policy. Keep the request ID if the problem continues, and check the service status page.
Documentation
Related support articles
Fix an authentication or permission error
Troubleshoot missing keys, revoked credentials, and features your organization cannot use.
Fix a request validation error
Use supported options, valid JSON, and the correct capture endpoint.
Use async jobs for longer captures
Submit a job, check its status, and download the result only after completion.
Need help with this issue?
Email support with this article, your request or capture ID, and the result you expected. Remove credentials and private information first.
Email [email protected]