Source and enrich candidate contact data using the hireEZ (formerly Hiretual) Talent Refresh API
domain: recruiting · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a hireEZ account and API key through your hireEZ admin console or an approved partner/embedded-integration agreement — enrichment access is provisioned per customer, not an open self-serve signup
Identify the candidate record(s) needing a refresh using an identifier hireEZ can match, such as an email address, LinkedIn/profile URL, or existing hireEZ candidate ID
Call hireEZ's Talent Refresh/enrichment API with your API key and the candidate identifier(s) to request updated contact info, work history, and resume data
Map the returned fields (emails, phone numbers, resume links, profile insights) back into your ATS or CRM candidate record
Timestamp and log which fields were changed by the enrichment call so downstream systems can distinguish hireEZ-sourced updates from manual recruiter edits
Re-validate consent/compliance requirements before using newly surfaced contact details for outreach
Known gotchas
hireEZ does not publish a fully open public REST reference for this API — it's typically surfaced through provisioned partner integrations (e.g. an 'Enrich with hireEZ' action embedded in another ATS), so confirm current endpoint/auth details with your hireEZ account team rather than assuming a generic path
This is a separate product and credential set from Gem's talent CRM — do not reuse Gem API keys or assume shared data models
Refreshed contact data can be stale or mismatched to the wrong person; verify before contacting candidates, especially under CAN-SPAM/GDPR-style consent rules
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?