Handle SmartRecruiters Posting/Customer API rate limits, concurrency limits, and offset pagination
domain: smartrecruiters.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Paginate list endpoints using offset and limit query params, reading totalFound from the response's ListResult wrapper (SmartRecruiters does not use page/pageSize).
Watch the X-RateLimit-Limit and X-RateLimit-Remaining response headers — most Customer API endpoints allow about 10 requests/sec.
Note tighter per-endpoint limits: roughly 2 req/sec for job publication (POST/DELETE /jobs/{id}/publication) and offer-document downloads.
Track concurrency separately via X-RateLimit-Concurrent-Limit/Remaining — most endpoints cap at 8 concurrent requests, but GET /candidates is capped at 1.
For bulk data needs, use the Reporting API instead of paginating the Posting/Candidates API directly.
Set client timeouts of 128 seconds or more and randomize request timing to avoid synchronized retry storms.
Known gotchas
GET /candidates allows only 1 concurrent request — parallelizing candidate pulls across threads triggers 429s immediately.
Rate limits vary per endpoint, not just per API — don't assume a single global budget across all calls.
Bulk-exporting through the transactional Posting/Candidates API instead of the Reporting API hits concurrency ceilings fast.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?