Scrapfly · Rate Limits

Scrapfly Rate Limits

Scrapfly does not advertise per-second request limits. Throttling is enforced primarily through account-level concurrency caps (set by subscription tier) and credit-pool exhaustion. Per-domain throttling may also engage. The API surfaces concurrency and credit state in response headers, and returns 429 when concurrency, free quota, or domain throttling is hit.

7 Limits Throttle: 429 Quota: 429
Web ScrapingData ExtractionRate Limiting

Limits

Free concurrency account
concurrent_requests
5
Applies to Free tier.
Discovery concurrency account
concurrent_requests
5
Applies to Discovery ($30/mo) tier.
Pro concurrency account
concurrent_requests
20
Applies to Pro ($100/mo) tier.
Startup concurrency account
concurrent_requests
50
Applies to Startup ($250/mo) tier.
Enterprise concurrency account
concurrent_requests
100
Applies to Enterprise ($500/mo) tier.
Custom concurrency account
concurrent_requests
negotiated
Custom plans negotiate concurrency above 100.
Per-domain throttling account/domain
varies
see Scrapfly throttling rules
Scrapfly may throttle a specific destination domain to protect target sites; surfaced as 429.

Policies

Concurrency-based throttling
Subscription tier sets the maximum simultaneously open scrape requests. Excess requests are rejected with 429 rather than queued.
Credit pool overflow
Free and Discovery plans hard-cap at the monthly credit quota. Pro and higher plans auto-bill overflow credits at tier-specific block rates ($1.20–$5.00 per 10,000 credits).
Backoff
On 429 responses clients should back off and retry, monitoring X-Scrapfly-Account-Remaining-Concurrent-Usage to gauge headroom.
Project-scoped limits
Concurrency can be sub-divided across Scrapfly Projects; project-level usage is reported via X-Scrapfly-Project-Concurrent-Usage.

Sources