Recruiting use case

Verify candidate & HM emails before talent outreach

Recruiting teams enrich from LinkedIn, seek tools, and scraped sources — then sequence hiring managers and candidates. Bad emails waste sequences and hurt domain reputation with employers. Verifly gates outreach lists with pay-as-you-go credits: API, CSV, Clay, or Zapier — no monthly verifier seat.

Verify a candidate emailAPI
curl -X GET "https://verifly.email/api/v1/verify?email={{candidate.email}}" \
  -H "Authorization: Bearer vf_your_api_key"

Real-time SMTP mailbox checks

Single, batch, and async bulk verification

Disposable, role account, and catch-all detection

Pay-as-you-go credits with no subscription lock-in

Search fit

Built for recruiting email verification

Use Verifly when you need a simple API, predictable pricing, and clean JSON results before emails hit your product, CRM, or campaign tool.

Clean enrichment exports before Instantly/Smartlead/Salesforge recruiting campaigns
ATS import hygiene: verify before loading candidate emails into Greenhouse/Lever/Ashby
Agency recruiting desks: one credit pool across client employer brands
Zapier/Make: new candidate row → verify → only then notify or sequence

Why recruiting lists bounce

Candidate emails are often personal Gmail/Outlook plus guessed corporate patterns for hiring managers. Enrichment tools propose permutations; only some mailboxes exist. Sequencing all of them creates hard bounces that damage the sending domain you use to represent employer brands.

Verifly returns deliverable / undeliverable / risky with disposable, role, and catch-all flags so you can keep personal inboxes, drop dead corporate guesses, and triage catch-alls.

Recruiting pipeline with Verifly

Source → enrich → Verifly → ATS or sequencer. For permutation-heavy HM outreach, verify every guess and keep only deliverable before the first touch.

  1. Export candidate/HM emails from your enricher or sheet.
  2. Batch or bulk verify with a vf_ key.
  3. Push deliverable rows to ATS and/or recruiting sequencer.
  4. Report list quality to hiring managers / client employers.
Batch verify HM permutations
curl -X POST "https://verifly.email/api/v1/verify/batch" \
  -H "Authorization: Bearer vf_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"emails":["j.smith@acme.com","john.smith@acme.com","jsmith@acme.com"]}'

PAYG fits recruiting volume

Reqs open and close. Monthly verifier seats do not match sprint hiring. Prepaid Verifly credits wait between reqs and cover surge weeks when multiple roles kick off.

hello@veriflyemail.com — only contact route.

FAQ

Frequently asked questions

Should we verify personal Gmail addresses?

Yes if you plan to email them. Syntax-valid Gmail can still be abandoned. Verifly mailbox checks reduce sends to dead personal inboxes.

What about role addresses like jobs@ or careers@?

Verifly flags role accounts. Useful for sourcing pages, usually wrong for personalized HM outreach — filter by your playbook.

Can we verify inside our ATS?

Use API/CSV/Zapier before or during import. Write a custom field for verifly_result if you want list views inside the ATS.

How is this different from SaaS outbound?

Same API; different list shape (candidates + HMs vs ICP leads). See /use-cases/saas-outbound for product-led outbound motions.

Ready to wire this?

Start free with 100 credits, mint a vf_ API key, and paste the recipe above. Buy a pack only when you need more — credits never expire.