Integrate with Workable's SPI namespace and Sourcing Tool Partner Program to push sourced candidates
domain: workable.readme.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Understand that "SPI" (Sourcing Partner Interface) is not a separate product — it's the /spi/v3/ URL prefix on the same Workable v3 API (e.g. GET https://{subdomain}.workable.com/spi/v3/jobs).
Apply to Workable's Sourcing Tool Integration partner program if you're building a multi-account sourcing vendor integration rather than a single-account tool.
Authenticate with an API access token, a partner token, or OAuth depending on whether you're a single-account integration or an approved partner.
Paginate results with limit (default 50) plus since_id/max_id cursor params, and filter with created_after/updated_after.
Push sourced candidates into a job's "sourced" pipeline stage using the same v3/SPI endpoints, scoped by your partner-specific permissions.
Verify inbound webhook payloads using the X-Workable-Signature HMAC-SHA256 header before processing.
Known gotchas
Workable enforces a documented 10 requests per 10 seconds limit — bursts beyond this return 429.
Recruiting-type webhook events require an args filter object (job_shortcode/stage_slug); omitting it can silently deliver no events.
The partner sourcing program is a gating/approval process, not a technically distinct API — don't expect different endpoint names once approved.
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?