Rate Limiting
Each API key has a rate limit applied to it. This protects the shared LinkedIn session and keeps scraping activity within safe bounds.Your rate limit
Every key is assigned a requests-per-second (RPS) limit when it is created. The default is:- 0.2 requests per second (12 requests per minute)
- Configured per key — contact your provider if you need a higher limit
When you exceed the limit
If you send requests faster than your key allows, the API responds with429 Too Many Requests:
Retry-After header indicating how many seconds to wait before retrying.
Handling 429s
Implement exponential backoff with jitter in your client code. Here’s a Python example:Tips for staying within limits
The API also enforces built-in delays between scraping requests to protect the underlying LinkedIn session. Your requests may take longer than expected even if you’re under your RPS limit.
- Space out requests — add a delay of at least 5 seconds between calls to stay safely under the limit
- Cache results — avoid re-scraping the same search by storing responses locally
- Use pagination efficiently — each
/scrapecall returns 25 items, so you only need one call per page (see Pagination) - Monitor your usage — if you consistently hit 429s, contact your provider about raising your RPS limit
Next steps
- Pagination — page through results efficiently
- Scrape API Reference — full endpoint documentation