Concurrency limits

Scrappey gives new accounts up to 200 concurrent threads by default and scales automatically up to 1000, with higher limits available on request.

Scrappey allows all new registered users to start with up to 200 concurrent threads by default.
This is more than enough for the majority of use cases and ensures smooth performance and fair resource distribution.

If your project requires more, Scrappey makes it easy to scale.

We automatically allow increases up to 1000 concurrent threads without manual review, provided:

• Your overall success rate is above 50%.
• You are following our general API guidelines.
• You are not abusing endpoints.

If you require more than 1000 concurrent threads, this is no problem — simply reach out to support with a short explanation of your use case.

We generally approve higher limits quickly for:

• High-throughput data pipelines
• Large-scale monitoring, indexing, and QA workloads
• Long-running automation workflows that require sustained concurrency

There is no hard upper limit as long as your use case fits within reasonable resource bounds and success rates remain healthy.

• Monitor your success rate regularly in the dashboard.
• Increase threads gradually to avoid sudden overload.
• If you encounter issues, check error codes in the docs first.

Concurrency is not a request parameter — it's simply how many requests you have in flight at the same time. Each simultaneous request consumes one thread. Fire requests in parallel from your own code and Scrappey processes them concurrently up to your account limit:

If you exceed your allotted threads, additional requests queue until a thread frees up. Keep your concurrent count at or below your limit to avoid delays.