June Offer Every MAX plan gets a fully custom-built system Free custom system worth $1,500-$10,000 · worth $1,500-$10,000

Twilio SendGrid SMTP Setup (2026): API Key + the apikey U...

Twilio SendGrid SMTP Setup (2026): API Key + the 'apikey' Username Trap

|6 min read|
Twilio SendGrid SMTP Setup (2026): API Key + the 'apikey' Username Trap
Matt KielbasaMatt Kielbasa6 min read

Built for transactional and bulk. The SMTP username is a literal string (the word "apikey"), not your account email. This trips up almost everyone setting it up for the first time.

SendGrid SMTP values
SMTP host
smtp.sendgrid.net
Port (recommended)
587 (STARTTLS)
Other ports
25, 2525 (unencrypted/TLS), 465 (SSL)
Username
apikey ← literally the lowercase word 'apikey'
Password
Your SendGrid API key (starts with SG.)

Create your SendGrid API key

  1. Sign in at app.sendgrid.com.
  2. Left sidebar, SettingsAPI Keys.
  3. Click Create API Key (top-right).
  4. Name it (e.g. "Inflowave SMTP").
  5. Choose permissions:
    • Restricted Access (recommended) → scroll to Mail Send → set to Full Access.
    • OR Full Access if you want the same key to manage templates, suppressions, etc.
  6. Click Create & View.
  7. Copy the API key immediately - SendGrid shows it once and never again. The key starts with SG. and is ~69 characters long.

Connect to Inflowave

  1. Inflowave → SettingsEmailAdd sending domainSendGrid (or Custom SMTP).
  2. Host: smtp.sendgrid.net
  3. Port: 587
  4. Username: apikey (exactly this word, lowercase, no quotes)
  5. Password: paste the SG.xxx key (no whitespace, no trailing newline - SMTP is line-oriented and a stray newline corrupts auth)
  6. Save, send a test.

Why "apikey"?: The SendGrid SMTP layer treats the username as a fixed identifier and authenticates entirely on the API key in the password field. The literal string is required - putting your account email there returns "535 Authentication failed".

Troubleshooting

"535 Authentication failed"

Username is not the literal "apikey", OR the API key has a typo / extra whitespace, OR the key lacks Mail Send permission. Regenerate with Restricted Access + Mail Send Full Access.

"550 The from address does not match a verified Sender Identity"

SendGrid requires you to verify either the From email or the From domain before sending. Settings → Sender Authentication → verify the domain via DNS records.

Auth succeeds but messages bounce

Domain authentication (SPF + DKIM via SendGrid) is not complete. Verify the CNAME and TXT records SendGrid showed you when you added the domain.

Connection and concurrency limits

  • 5,000 messages per SMTP connection. Above that, the connection is dropped and you reconnect. Inflowave reconnects automatically; you do not need to manage this.
  • 10,000 concurrent SMTP connections from a single sending IP. Plenty for any single-tenant Inflowave workspace.
  • Do not hardcode IPs: SendGrid rotates the IPs behind smtp.sendgrid.net without notice. Always use the hostname; never lock to an IP.
  • Daily volume caps depend on your SendGrid plan - Free is 100/day, Essentials starts at 50,000/month, Pro and above are uncapped subject to reputation.

Official sources

2026 OPERATOR REPORT

The Agency Profit Playbook Is In

How do 80+ agency operators rate their own pricing, retention, and margin? The Agency Profit Playbook has the benchmarks.

You can unsubscribe in one click. Privacy Policy

The Agency Profit Playbook 2026 cover

Ready to send through SendGrid?

Username is literally the word 'apikey' - not your account email. That's the #1 setup mistake.