Yes, IPRoyal Web Scraper API has a concurrency limit for each account, which is the number of scrape requests that can run at the same time. The limit applies to scrape requests (POST /v1/scrape), not to the number of requests you send in total.
How to Check Your Concurrency Limit
Use the User endpoint (GET /v1/user). The ‘concurrency_limit’ field in the response shows how many scrape requests you can run at once:
{
"credit_amount": 48250,
"status": "active",
"concurrency_limit": 50
}
What Happens When You Reach the Limit
If you send a new scrape request while the maximum number of requests is already running, you’ll get a ‘429 concurrency_limit_exceeded’ error. Requests rejected for this reason don’t use credits.
To fix it, wait for a running request to finish, then retry. To avoid the error, keep the number of requests running in parallel below your limit.
Note: A ‘503 capacity_exceeded’ error is different. It means the service as a whole is at full capacity, regardless of your own limit. Retry after a few seconds with backoff.
How to Increase Your Concurrency Limit
If you want to increase your account’s concurrency limit, contact IPRoyal Support at [email protected].
To learn more, see our Web Scraper API documentation.