SendGrid for Bulk Email: Configuration and Limits

SendGrid is one of the most common platforms for bulk email — partly because it's mature, partly because it bundles with Twilio products, and partly because it has the kind of brand recognition that makes it the default pick for developers who don't want to research alternatives. Whether it's the right choice for your bulk email use case is a separate question.

This guide covers configuration, sending limits, and the practical considerations for using SendGrid at bulk volumes. If you're evaluating SendGrid against alternatives, see our SendGrid review and comparisons like SendGrid vs Mailgun.

Two Paths: Marketing Campaigns vs. API

SendGrid has two surfaces for bulk sending:

Marketing Campaigns

The UI-based path for marketing teams. You log in, build an email in the drag-and-drop editor, select a segment, and schedule a send. Includes:

• Template library and editor
• List segmentation
• A/B testing
• Automation flows
• Click and open analytics

Best for: traditional email marketing teams without engineering involvement.

v3 Mail Send API

The programmatic path for developers. You send a JSON POST to /v3/mail/send with one or more personalizations (each containing recipients). Includes:

• Up to 1,000 recipients per API call
• Per-recipient template substitutions
• Categories and custom args for tracking
• Send scheduling

Best for: SaaS applications, transactional sending, programmatic marketing.

For bulk sending via API, you typically batch calls — each request can contain up to 1,000 personalizations (one personalization per recipient), and you make multiple requests to hit higher volumes.

Authentication Setup

Before sending bulk through SendGrid, configure sender authentication:

1. Sender Authentication > Authenticate Your Domain
2. SendGrid generates CNAME records for DKIM and a CNAME for return-path
3. Add these CNAMEs to your DNS provider
4. Click "Verify" — SendGrid checks DNS and confirms

Authenticated domains pass DMARC alignment. Unauthenticated sending shows via sendgrid.net in Gmail's "show original" view and fails DMARC, which kills deliverability for any sender with a DMARC policy beyond p=none.

You also need to publish your own SPF record including SendGrid's directive:

v=spf1 include:sendgrid.net ~all

If you use multiple ESPs, your SPF record must include each one's directive. See SPF flattening if you hit the 10-DNS-lookup SPF limit.

Practitioner note: The most common SendGrid authentication mistake I see is configuring "Domain Authentication" but not publishing your own SPF record. Domain Authentication handles SendGrid's side; the SPF record on your sending domain is your responsibility. Without it, mailbox providers can't validate that you authorized SendGrid to send for your domain, and DMARC fails despite a green checkmark in the SendGrid UI.

Sending Limits by Plan

SendGrid's plan structure as of 2026:

Plan	Monthly Volume	Per-Day	Cost (USD)
Free	3,000	100	$0
Essentials	50,000	varies	$20
Essentials	100,000	varies	$35
Pro	100,000	varies	$90
Pro	300,000	varies	$250
Premier	Custom	Custom	Custom (~$1K+)

Pro and above include dedicated IP options. Premier includes account management and advanced compliance support.

API Rate Limits

Beyond plan-level volume:

• 600 API requests per second (Mail Send endpoint)
• 1,000 personalizations per API call
• Throttle adjustments via support for Enterprise

A practical bulk strategy: batch 1,000 recipients per call, hit 600 calls/second max, achieve up to 600K sends per second. Real-world throughput is lower due to ISP receive-side throttling.

Configuring a Bulk Send

Via Marketing Campaigns UI

1. Build a Single Send or Automated send
2. Select your list and any segment filters
3. Configure subject, preheader, from/reply-to addresses
4. Run the design test (renders across major clients)
5. Send test to seed addresses
6. Schedule send or send immediately
7. Monitor stats page during and after send

Via API

curl --request POST \
  --url https://api.sendgrid.com/v3/mail/send \
  --header "Authorization: Bearer $SENDGRID_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "personalizations": [
      {"to": [{"email": "[email protected]"}], "subject": "Hi user1"},
      {"to": [{"email": "[email protected]"}], "subject": "Hi user2"}
    ],
    "from": {"email": "[email protected]"},
    "content": [{"type": "text/html", "value": "<p>Body</p>"}]
  }'

For real bulk, batch personalizations into arrays of 1,000 per request. Use unique substitutions per recipient for personalization rather than calling the API once per recipient.

Suppression List Management

SendGrid maintains automatic suppression for:

• Bounces: hard bounces auto-suppressed
• Spam reports: complaints auto-suppressed via feedback loop
• Unsubscribes: one-click unsubscribes auto-suppressed
• Global unsubscribes: account-level opt-outs
• Group unsubscribes: per-category opt-outs

Bypass headers (X-SMTPAPI) can override suppressions for transactional mail — use sparingly and only for true transactional (receipts, password resets).

When SendGrid Suspends Bulk Accounts

SendGrid's compliance team monitors:

• Bounce rate above 5%
• Spam complaint rate above 0.08%
• Sending to unverified sender domains
• Sudden volume spikes from new accounts
• Sending patterns matching cold outreach (against ToS)

Suspensions usually come with email warnings first. Common triggers:

• Importing purchased lists
• Sending cold outreach (SendGrid prohibits this on most plans)
• Failing to suppress bounces and continuing to send
• New accounts pushing 100K+ on day one

Practitioner note: SendGrid is strict about cold outreach. If you import a list of prospects and start sending, expect account suspension within hours. The ToS is explicit — opt-in lists only. For cold outreach, use a dedicated platform built for that use case, not SendGrid. See our cold email infrastructure guide for what to use instead.

Bulk Email Best Practices on SendGrid

• Use Marketing Campaigns for newsletters, API for transactional
• Warm up new sending domains for 4-6 weeks before high volume
• Authenticate domains properly before any production send
• Set up dedicated IPs if sending above 200K/month
• Monitor stats daily for bounce/complaint spikes
• Use categories to segment sends in reporting
• Implement list-unsubscribe header for any marketing send

When to Use Something Else

SendGrid is fine for most use cases but isn't always the best pick:

• High-volume, cost-conscious: AWS SES is 5-10x cheaper
• Marketing UI, ease of use: Brevo is easier and cheaper
• Pure transactional deliverability: Postmark consistently outperforms
• Cold outreach: Don't use SendGrid (ToS violation); use Instantly or Smartlead
• Ecommerce automation: Klaviyo is better for Shopify

If you're trying to figure out whether SendGrid is right for your bulk email use case, or migrating from SendGrid to a better-fit alternative, book a consultation. I work with operators on ESP selection and migration.

Sources

• SendGrid: Mail Send API v3
• SendGrid: Sender Authentication
• SendGrid: Pricing
• SendGrid: Rate Limits
• RFC 8058: List-Unsubscribe-Post

---

v1.0 · May 2026