Connect your own SendGrid account
A mail API you can reach with a restricted key. SendGrid returns the message id in a response header, and that id is what the send log stores.
What you need from SendGrid
Gather these in the SendGrid portal first. The connection form asks for exactly these fields and nothing more.
| Field | What it is |
|---|---|
| apiKey | API Key. A restricted key with permission to send mail. |
Credentials are sealed with AES-256-GCM and the console only ever shows a masked value afterwards. Plaintext is never written to logs and never sent back to the browser.
What we configure on the connection
- Sender address (From). Must be an address on a domain you have verified in SendGrid.
- Default send pacing: 10 messages per second. This is a conservative starting point, applied per connection, and you can change it at any time. Your real ceiling is set by SendGrid — check your account quota and raise the value to match.
Why teams pick SendGrid
- Restricted keys, so sending can be granted without granting account access
- A conventional mail API surface and error vocabulary
- Domain verification stays in your own SendGrid account
Worth knowing
- The message id comes back in the X-Message-Id response header; a 2xx without one is treated as a failed send rather than a success.
What stays on your side
These are yours to hold — and that is the point of bringing your own account: the relationship, the rates and the compliance stay in your name, not ours.
- Account approval and billing terms
- Domain verification, plus the SPF and DKIM records for the domain you send from
- Sender reputation, and any blocklist remediation that follows from it
- The quotas and rate limits SendGrid grants your account
Next
Whaleal Platform currently offers self-service connections to 6 SMS providers, 4 email providers and 3 WhatsApp providers. Underlying the SMS channel is an SMS adapter library of 33 adapters; the ones outside this list are unlocked on request rather than self-service.