Email Verification API vs. Bulk: Which Should You Choose?

Two Ways to Verify

SendSure offers two primary verification methods: a real-time API that verifies individual emails in under 3 seconds, and a bulk upload system that processes CSV files at 30,000 emails per minute. Both use the same 27-stage verification engine — the difference is in how you feed emails into it and when you get results.

Choosing the right method depends on your use case, technical requirements, and volume. Here's how to decide.

Real-Time API Verification

How It Works

You send a single email address to our REST API endpoint, and within 1-3 seconds you get back a detailed verification result including status, risk score, sub-status, and reason codes.

POST /api/verify/single
{
  "email": "john@example.com"
}

Response:

{
  "status": "valid",
  "quality_score": 0.95,
  "sub_status": "deliverable",
  "risk_band": "low",
  "reason_codes": ["smtp_valid", "mx_found", "not_disposable"]
}

Best Use Cases

Signup forms and registration. Verify emails at the point of entry before they ever enter your database. If the email is invalid, show an error message immediately. This is the highest-ROI use of real-time verification — preventing bad data is always cheaper than cleaning it later.

Lead capture pages. When a visitor submits their email on a landing page or gated content form, verify it in real-time. This ensures your sales team only follows up on real email addresses.

CRM data entry. When sales reps manually enter email addresses, trigger a verification check before saving to the CRM. This prevents human typos from polluting your database.

Checkout flows. For e-commerce, verify the email during checkout to ensure order confirmations and receipts are deliverable.

Technical Considerations

• Latency: 1-3 seconds per email. This is fast enough for form validation but adds noticeable delay if you're verifying hundreds of emails sequentially.
• Rate limits: Depends on your plan. Growth plans support 100 verifications per minute; Enterprise goes up to 500/min.
• Cost: 1 credit per verification. Same cost as bulk — no premium for real-time.
• Error handling: Your integration should gracefully handle timeouts and 429 (rate limit) responses.

Integration Patterns

Synchronous validation (recommended for forms):

The user submits the form, your backend calls the API, and you return the result before the page reloads. If the email is invalid, show a validation error.

Asynchronous validation (recommended for APIs):

Fire the verification request in the background and store the result. Don't block the user experience. Update the email's status in your database when the result arrives.

Webhook-based (for high volume):

Submit emails for verification and receive results via webhook callback. This decouples the verification from your request/response cycle.

Bulk CSV Upload

How It Works

Upload a CSV or Excel file containing email addresses (and optionally other columns like name, company, etc.). SendSure processes the entire file through the 27-stage engine at up to 30,000 emails per minute, then provides a downloadable results file.

Best Use Cases

Quarterly list cleaning. Export your email list from your ESP, upload to SendSure, download the cleaned results, and re-import. This is the most common use of bulk verification.

Pre-campaign verification. Before launching a major email campaign, run your send list through bulk verification to catch any addresses that have gone bad since the last check.

List import validation. When importing a purchased, rented, or partner-shared email list, run it through bulk verification before adding any addresses to your database.

Database migration. When switching ESPs or CRMs, verify your entire list as part of the migration to start clean on the new platform.

Technical Considerations

• Throughput: Up to 30,000 emails per minute for paid plans. A list of 100,000 emails takes roughly 3-4 minutes.
• File formats: CSV, Excel (.xlsx), and .txt (one email per line) are all supported.
• Column detection: SendSure automatically detects the email column. Other columns (name, company) are preserved in the output file.
• Results download: The output CSV includes all original columns plus verification status, quality score, risk band, and reason codes.
• Maximum file size: 100MB per upload (roughly 2-3 million emails depending on column count).

Head-to-Head Comparison

| Factor | Real-Time API | Bulk Upload | |--------|--------------|-------------| | Speed per email | 1-3 seconds | Varies (batch processing) | | Throughput | 100-500/min (rate limited) | 30,000/min | | Integration effort | Medium (API integration) | Low (CSV upload) | | Best for | Point-of-entry validation | List cleaning | | Cost per email | 1 credit | 1 credit | | Automation | Fully automatable | Manual or CRM sync | | Results format | JSON response | Downloadable CSV |

The Hybrid Approach (Recommended)

The best email verification strategy uses both methods:

Real-time API at the point of entry. Catch bad emails before they enter your database. This prevents the problem rather than fixing it later.

Bulk verification on a schedule. Even with point-of-entry validation, email addresses go bad over time. Run bulk verification quarterly (or monthly for large lists) to catch addresses that have become invalid since they were first verified.

CRM sync for automation. Connect SendSure to your ESP (Mailchimp, HubSpot, SendGrid) for bi-directional sync. SendSure will automatically verify new contacts and flag addresses that go bad — no manual CSV uploads needed.

Implementation Example

Here's what a complete verification strategy looks like:

1. Signup form — Real-time API verification before account creation
2. Lead forms — SendSure form widget (2 lines of code, no backend needed)
3. CRM import — Bulk verification of any imported lists
4. Monthly sync — SendSure CRM connector runs monthly verification passes
5. Pre-campaign — Automated bulk verification triggered 24 hours before scheduled sends

This layered approach ensures your list stays clean from entry through ongoing maintenance.

Which Should You Start With?

If you're a developer building a product with email input, start with the real-time API. Add verification to your signup flow first — it has the highest ROI and prevents bad data at the source.

If you're a marketer cleaning an existing list, start with bulk upload. Upload your list, download the results, and remove invalid addresses before your next campaign.

If you have budget for both, implement the hybrid approach. The real-time API prevents new bad data, and bulk verification catches addresses that decay over time.

All methods use the same 27-stage verification engine and cost the same per email. The only difference is how you access them. Start with 100 free credits and try both — you'll quickly see which fits your workflow.