Solution skill
SendGrid 403 access forbidden on mail send: the key lacks Mail Send scope
Complete solution
Shows how to fix sendGrid 403 access forbidden on mail send: the key lacks Mail Send scope. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Check the key's permissions: Settings > API Keys > the key > Edit. Fix: create a new key with Restricted Access granting Mail Send (Full Access under Mail Send is the usual pick), deploy it, then delete the under-scoped key.
Steps
- Symptom: the key authenticates (no 401) but POST /v3/mail/send returns 403 access forbidden.
- Read the errors array. If the message is about access rather than the sender identity, it is a scope problem.
- Check the key's permissions: Settings > API Keys > the key > Edit. A Mail Send restricted key can send mail but cannot read suppressions, manage templates, or touch stats.
- Fix: create a new key with Restricted Access granting Mail Send (Full Access under Mail Send is the usual pick), deploy it, then delete the under-scoped key.
- Do not fix a 403 by switching to Full Access in production. Full Access grants every endpoint; it is a development convenience, not a production posture.
- Remember a key can never have greater permissions than the user who created it. If the creator is a restricted teammate, the key inherits that ceiling.
- If the 403 message is instead about the from address not matching a verified Sender Identity, that is a different 403: see the sender-identity skill.
When to use
You are seeing this: Symptom: the key authenticates (no 401) but POST /v3/mail/send returns 403 access forbidden. Use this skill when you run into "SendGrid 403 access forbidden on mail send: the key lacks Mail Send scope".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Edge cases
- Remember a key can never have greater permissions than the user who created it.
Evidence
The errors doc lists 403 as access forbidden. The API keys doc: keys cap at 100 per account, a key can never exceed its creator's permissions, and scopes include Full Access, Restricted (custom) access, Billing, and Email Validation access. A Restricted key without Mail Send authenticates fine and is then forbidden from sending. Sources: https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/errors | https://docs.sendgrid.com/ui/account-and-settings/api-keys
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Nj39_JYDXkMwryeR1Newtw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">SendGrid 403 access forbidden on mail send: the key lacks Mail Send scope <span>— Vectle</span></a>