KeyKeeperTwilio SendGrid · EU regional subuser
How an agent gets a Twilio SendGrid · EU regional subuser key through KeyKeeper, what to choose on app.sendgrid.com, and how KeyKeeper verifies it.
| Template id | sendgrid-eu |
|---|---|
| Field | sendgrid-api-key → SENDGRID_API_KEY · secret |
| Also | sendgrid-api-base → SENDGRID_API_BASE · plain, confirmed by you |
| Key looks like | starts with SG., shown once when created |
| Created at | app.sendgrid.com |
| Verified by KeyKeeper | not verified |
| Template checked | 2026-09-15 |
What the agent does
keykeeper providers show sendgrid-eu
keykeeper save --provider sendgrid-eu --from-clipboard --create --purpose "what this task does"
keykeeper run -c sendgrid-eu -- <your command>--provider sendgrid-eu fills in the credential id and the fields. The environment
variables are the ones Twilio SendGrid's own tools read, so nothing has to be mapped.
What only you can do
Sign in to the EU regional subuser
Create an API key
Choose Custom Access
Copy the key, then approve the save in KeyKeeper's window.
What to choose
Choose Custom Access and enable only Mail Send. Use the EU API base for this regional subuser.
The agent is told the same thing. It opens the page for you and says what to pick; it never logs in, passes 2FA or pays on your behalf.
What KeyKeeper checks
- Before writing: the value must look like a Twilio SendGrid · EU regional subuser key (starts with
SG., shown once when created). A wrong paste is refused before anything is stored, and the agent is told why — without the value. - After saving: Twilio SendGrid · EU regional subuser offers no read-only endpoint KeyKeeper can use, so the first real call is the test.
Rotation and expiry
No universal expiry policy was confirmed for this credential type. Record the date shown by the provider, or leave it unknown. Rotate or revoke at app.sendgrid.com.