Authenticate with the SmartRecruiters API using your API key (YOUR_SR_API_KEY) passed in the X-SmartToken header for all requests.
Configure a SmartRecruiters webhook subscription for the candidate hired event so your integration is notified in real time when a candidate is moved to Hired status.
On receipt of the hired event webhook, extract the candidate ID and job ID from the payload, then make a GET request to the candidates endpoint to retrieve full candidate profile data including contact information, custom fields, and offer details.
Map the SmartRecruiters candidate fields to your HRIS schema; pay particular attention to custom fields that hold offer-specific data such as compensation, start date, and employment type.
POST the mapped employee record to the HRIS to create the pre-hire or new employee entry and capture the HRIS employee ID.
Write the HRIS employee ID back to the SmartRecruiters candidate record using a custom field update via the API, establishing a cross-system link for future status synchronization.
Known gotchas
SmartRecruiters webhook payloads contain minimal data — they primarily signal that an event occurred and include IDs but not full candidate profiles; always follow up with an explicit API call to retrieve the full record before attempting to push to an HRIS.
Custom field values in SmartRecruiters are schema-dependent and vary by account configuration; hardcoding field IDs from one customer's account will break when used against another account's configuration.
The hired status in SmartRecruiters can be reversed (candidate un-hired) — implement a handler for status reversal events to avoid maintaining phantom employee records in the HRIS.
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