Outbound recruiting lists die when candidate or hiring-manager emails bounce. Here is a practical verify-before-send workflow that keeps domains healthy without a monthly verifier seat.
The problem
Recruiting teams pull emails from LinkedIn exports, ATS CSVs, enrichment tools, and referral sheets. A 10–20% undeliverable rate is common. Hard bounces burn sending domains and waste SDR/recruiter time.
The pattern
- Collect candidate / HM emails into a sheet or Clay table.
- Verify with a pay-as-you-go API (real-time or batch).
- Keep only
deliverablerows (fail closed on disposable / role if that matches your policy). - Push clean rows into your sequencer or personal outreach.
Canonical walkthrough: Recruiting use case on Verifly
HTTP verify (single address)
curl -X GET "https://verifly.email/api/v1/verify?email=candidate@company.com" \
-H "Authorization: Bearer vf_your_api_key"
Use the same call from Clay HTTP enrichment, n8n HTTP Request, Zapier Webhooks, or Make.
Batch sketch
POST https://verifly.email/api/v1/verify/batch with up to 100 emails per request. For larger ATS dumps, use async bulk (see docs).
Why PAYG fits recruiting
Hiring volume is bursty. A monthly verifier seat bills quiet weeks. Prepaid credits that never expire match sprint-based sourcing better.
Model cost: Credit calculator
Recipes
Agents
AI sourcing agents can call the same API or the hosted MCP endpoint at /mcp and share one credit pack with human workflows.
Built with Verifly — pay-as-you-go email verification. Contact: hello@veriflyemail.com
Top comments (0)