Integrate a Paradox (Olivia) AI recruiting assistant/chatbot with an ATS for automated screening and scheduling
domain: recruiting · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get credentialed as a Paradox customer/partner and obtain API credentials per the Paradox Developer Hub's Authentication guide
Use the Candidates endpoints (get/create/get-single) to push candidate records into Paradox or pull candidates Olivia has screened, and the Candidate Attributes endpoints to read/write custom screening responses
Use the Scheduling endpoints (interview settings, multiparty interviewers, job location rooms) to configure and retrieve interview scheduling data Olivia manages during conversational scheduling
Register webhooks via Paradox's webhook framework to receive real-time events (e.g., screening completed, interview scheduled) so your ATS updates candidate stage automatically instead of polling
For major platforms (Workday, SuccessFactors, Greenhouse, iCIMS, etc.) prefer Paradox's pre-built native integrations over custom API work, reserving direct API calls for gaps those connectors don't cover
Known gotchas
Paradox's 'open API' is still a partner/customer-gated platform - it requires an active Paradox account and issued credentials, not an anonymous self-serve signup
Bi-directional sync means status changes made manually in your ATS must be deliberately mapped back into Paradox (and vice versa), or Olivia can act on stale candidate-stage data, e.g., messaging someone already rejected in the ATS
The API surface is organized around Paradox's own data model (locations, rooms, areas, user permissions) rather than a generic ATS schema - expect to build a real mapping/normalization layer to your ATS's requisition/candidate model
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?