Production API traffic is subject to a shared limit of approximately 1,000 requests per public IP over 60 seconds. This applies to both hirers and agencies. Users and integrations sharing an office or server public IP contribute to the same limit, even when using different accounts or API keys.

Existing login, MCP and individual API-key limits also apply and may be lower. The shared limit does not increase an integration's individual allowance.

​

HTTP 413 means a request exceeds its payload size limit. Unlike a rate-limit response, waiting and sending the same oversized request will not resolve it. Reduce the payload or use the supported direct file-upload flow where available. This applies to both hirer and agency integrations.

​

Requests blocked by the shared IP limit receive HTTP 429 with the message Too many requests and a Retry-After header of 60 seconds. Wait at least that long before retrying, reduce request concurrency and spread bulk work over time. If traffic from the shared IP remains high, further requests may still be blocked.

If rate-limit responses continue during normal use, contact support with the approximate time and affected operation. Never include passwords, access tokens or API keys in a support message.