SendGrid email verification
Verify addresses before SendGrid sends them
SendGrid handles your transactional and marketing sends, and every bounce it records counts against your sender reputation. Verifly verifies addresses at collection time and cleans lists before send, so SendGrid's suppression list stays lean and your IP reputation stays high.
curl -X GET "https://verifly.email/api/v1/verify?email=user@example.com" \
-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 SendGrid 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.
Why verify before SendGrid, not after
SendGrid is a sending platform for both transactional mail — receipts, password resets, notifications — and marketing campaigns. It tracks bounces meticulously and maintains a suppression list: once an address hard-bounces, SendGrid stops sending to it. That protects you, but it means every bad address you feed in costs you a bounce event on your reputation before it lands on the suppression list. High bounce rates push mailbox providers to throttle or block your sending IP and domain.
The trouble with catching problems only at SendGrid is timing. By the time SendGrid suppresses an address, the bounce is already recorded against you, and for transactional mail a bounced receipt or password reset is a silent failure your user never sees. Verifying at the point of collection — the signup form, the checkout, the API that adds contacts — stops the dead address from ever entering your sending flow.
Verifly runs a live mailbox check and returns deliverable, undeliverable, or risky with disposable, role, and catch-all flags. Verify at collection to keep the database clean, and batch-verify marketing lists before a campaign so SendGrid records a low bounce rate and your suppression list only fills with genuinely dead mailboxes.
Add a verification step at collection
- Call GET /verify from your signup or checkout handler before writing the address to your database or SendGrid.
- Register a free key at verifly.email/api/v1/autonomous/register (100 credits, no card, no captcha).
- Reject or flag undeliverable and disposable results at the form so they never reach SendGrid.
- For existing marketing lists, POST them to /verify/batch before a Marketing Campaigns send and drop the bad rows.
- Send through SendGrid against verified addresses only, keeping bounces and suppressions minimal.
async function onSignup(email) {
const res = await fetch(
`https://verifly.email/api/v1/verify?email=${encodeURIComponent(email)}`,
{ headers: { 'Authorization': 'Bearer vf_your_api_key' } }
)
const data = await res.json()
if (data.result !== 'deliverable' || data.disposable) {
return { ok: false, reason: 'Please use a valid, permanent email address' }
}
// safe to store and send via SendGrid
return { ok: true }
}FAQ
Frequently asked questions
Doesn't SendGrid's suppression list already handle bounces?
It handles them after the fact — an address only lands on the suppression list once it has bounced, and that bounce is already counted against your reputation. Verifying before send prevents the bounce from happening at all.
Should I verify transactional emails too?
Yes. A bounced receipt or password reset is a silent failure the user never learns about. Verifying the address at signup ensures your critical transactional mail actually reaches a live mailbox.
Can I keep my SendGrid suppression list smaller?
Verifying before send means only genuinely dead mailboxes ever bounce and get suppressed, instead of typos and disposable addresses padding the list. A leaner suppression list is easier to reason about.
How does Verifly treat catch-all domains?
Catch-all domains accept any local part, so no verifier can confirm a specific mailbox. Verifly flags them as catch-all rather than guessing, and you decide whether to send based on your bounce tolerance.
What does verifying for SendGrid cost?
Pay-as-you-go from $2 per 1,000 checks down to $0.60 per 1,000 at volume, with 100 free credits to start and no monthly minimum, independent of your SendGrid plan.
Can I verify inline in my sending pipeline?
Yes. Call GET /verify for single addresses at collection or POST /verify/batch before a campaign send. The Verifly MCP server at verifly.email/mcp lets an AI agent trigger checks in an automated flow.