Authenticate with your SmartRecruiters API key by including the X-SmartToken: your-api-key header on all requests; for multi-customer apps use OAuth 2.0 instead
Retrieve a list of candidates by calling GET https://api.smartrecruiters.com/candidates; supported query parameters include keyword, jobId, status, location, and consentStatus for filtering
Paginate results using the pageId cursor returned in the response's nextPage field; continue until nextPage is absent or null
Retrieve the full profile of a specific candidate via GET https://api.smartrecruiters.com/candidates/{candidateId}; this includes personal details, application history, and screening answers
To retrieve a candidate's screening question answers for a specific job application, call GET https://api.smartrecruiters.com/candidates/{candidateId}/jobs/{jobId}/screening-answers
To retrieve offer information for a candidate on a specific job, call GET https://api.smartrecruiters.com/candidates/{candidateId}/jobs/{jobId}/offers
Known gotchas
The SmartRecruiters Candidates API returns candidates across all jobs; to scope results to a specific job's applicants, filter by jobId query parameter rather than calling a job-specific candidates endpoint
GDPR consent status is tracked at the candidate level; candidates who have withdrawn consent may be suppressed from results or return limited data — handle partial profiles gracefully
API key authentication (X-SmartToken) is scoped to a single SmartRecruiters account; if you are building a multi-tenant integration serving multiple SmartRecruiters customers, you must implement OAuth 2.0 rather than storing per-customer API keys
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp