The SendGrid from name isn't showing because the display name is in the wrong API field. Use from.name in the v3 Mail Send object, or fix SMTP/Sender setup.
Updated Jul 1, 2026
The short answer
"SendGrid from name not working" means the sender display name you set isn't showing in recipients' inboxes — they see only the bare email address, the wrong name, or the send is rejected. The usual cause is putting the name in the wrong place: SendGrid's v3 API expects a separate "name" field inside the "from" object. Fix the JSON structure, or set the name on a verified Sender.
The display name (the "from name") is the friendly label recipients see instead of a raw address — e.g. Acme Support <support@acme.com>. When it "isn't working," recipients usually see only the bare email address, an old/cached name, or the send fails outright. The cause is almost always where you put the name, not the name itself.
Most cases fall into one of these:
name field inside the from object. If you cram the name into the email value (e.g. "email": "Acme Support <support@acme.com>"), SendGrid treats the whole string as the address and either drops the name or returns a validation error.from.name; the legacy v2 Web API used a top-level fromname parameter; SMTP uses an RFC 5322 From header. Mixing them (e.g. sending fromname to v3) has no effect on the from name — v3 simply doesn't read that field.from address to belong to a verified Sender Identity — via Domain Authentication or Single Sender Verification. If the address isn't verified, the mail is blocked with "The from address does not match a verified Sender Identity" before the name ever matters.v3 Mail Send API (recommended) — put the name in its own field:
"from": {"email": "support@acme.com","name": "Acme Support"}
The name field is optional but, when present, must be a sibling of email — not embedded in it.
SMTP relay — format the header per RFC 5322 §3.6.2:
From: "Acme Support" <support@acme.com>
Legacy v2 Web API only — use the top-level fromname parameter (do not use this with v3; it is ignored there). Prefer migrating to v3.
Marketing Campaigns — set the name under Marketing > Senders (or Settings > Sender Authentication > Single Sender Verification), per SendGrid's Adding Sender Name guide.
Verify the sender first. If the email is rejected rather than just missing a name, authenticate the address — Domain Authentication (generates SPF/DKIM, lets you send from any address at the domain) or Single Sender Verification (single address, fine for testing) — then retry.
Sending through Courier? Courier's SendGrid integration is designed to pass your configured display name through to from.name. If it's not appearing, set it explicitly via the Courier provider override for SendGrid (any field on /mail/send can be overridden), and confirm the same address is a verified Sender in your SendGrid account.
After changing it, send a test to yourself and check the rendered From header — note that some inboxes cache a contact's display name, so test with an address that has never received mail from you.
References
SendGrid: Adding Sender Name or From Name to your Emails
DOCSTwilio SendGrid Docs: Mail Send API reference (from object)
HELPSendGrid: Validation Errors when Sending Emails Using the Mail Send API
DOCSTwilio SendGrid Docs: Authenticate a single sender / Sender Identity
RFCRFC 5322 §3.6.2 (originator fields / From header)
FAQ
The display name is in the wrong place. In SendGrid's v3 Mail Send API the name must be a separate field inside the from object — {"email": "you@domain.com", "name": "Your Name"} — not concatenated into the email value. If you put the name inside the email string, SendGrid parses the whole thing as the address and the name is dropped.
`fromname` is the top-level parameter from SendGrid's legacy v2 Web API. The current v3 Mail Send API instead uses a `name` field nested inside the `from` object. Sending `fromname` to v3 has no effect, which is a common reason the name silently fails to appear.
The address does. SendGrid requires the from email to belong to a verified Sender Identity (Domain Authentication or Single Sender Verification); otherwise the send is rejected entirely. The display name itself isn't verified, but it can't show if the underlying send is blocked for an unverified sender.
One API, every provider
Courier connects to your email, SMS, and push providers, handles retries and failover, and surfaces delivery errors in plain language.
Reply-code definitions per RFC 5322 §3.6.2. Last reviewed Jul 1, 2026. Courier is not affiliated with third-party providers; error behavior may vary by implementation.
© 2026 Courier. All rights reserved.