Async API documentation and concurrency clarifications
Refreshed Async API docs with clearer concurrency guidance, plus a new product surface shipped in the same release.
The Async API documentation has been refreshed. The two biggest clarifications:
A separate thread pool, not shared concurrency
The Async API runs in its own background thread pool, independent of your main API concurrency. You can hit https://api.scrape.do and https://q.scrape.do simultaneously without one blocking the other.
The pool sizes are equivalent to ~30% of your plan's main concurrency limit, but not deducted from it:
| Plan | Main API Concurrency | Async Concurrency (separate) |
|---|---|---|
| Free | 5 | 2 |
| Hobby | 5 | 2 |
| Pro | 15 | 5 |
| Business | 40 | 12 |
| Advanced | 200 | 60 |
Plugin scraping at scale
Every structured plugin endpoint (Amazon, Google Search, Google Trends, …) is now available through the Async API. Submit a batch, get a job ID back, poll for results — without managing retries, rate limits, or sessions yourself.
See the Async API documentation and the plugin reference for full request/response shapes.
