Workable: Creating candidates and attaching them to jobs
Blog post from Unified.to
Workable treats talent-pool candidates and job-specific candidates as separate records, so creating a person with the candidate endpoint produces a talent-pool ID, while attaching that person to a job through the application endpoint creates a distinct job-scoped candidate ID and application ID. Integrations should store both identifiers, using the new job-scoped candidate ID for later job-related retrievals or updates and avoiding repeated application creation with the original talent-pool ID, which would create duplicate copies. Candidate creation is safe to retry by email because Unified returns an existing talent-pool candidate when Workable rejects a duplicate, while searches by email may return both talent-pool and job-scoped records after an attachment. Changes to either record do not synchronize to the other, making native IDs necessary despite matching email addresses. Application creation also requires a Workable member ID, preferably supplied as a user ID, and email searches can help recover valid current IDs if an older ID returns a 404 error.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.