Send with SendGrid
To run a SendGrid newsletter self-hosted with ReputeCast, you need one SendGrid API key. ReputeCast registers a signed Event Webhook, authenticates your sending domain through the SendGrid API, turns SendGrid’s own tracking off on every message and keeps the suppression lists of both sides in sync.
| Kind | API |
|---|---|
| Bulk marketing | Allowed |
| Event webhooks | Signed Event Webhook registered by ReputeCast; ECDSA P-256, 26-hour window |
| Domain setup | API |
| Suppression sync | Two-way |
| Batch size | 1 |
| Notes | Reads the plan's email credits. One call per message. |
Before you begin
Section titled “Before you begin”- A SendGrid API key with Full Access (SendGrid › Settings › API Keys). ReputeCast uses it to send, register and sign the Event Webhook, authenticate domains, read and write suppressions, read tracking settings and statistics. A key restricted to fewer scopes connects, but the webhook, domain or suppression steps then fail with “access forbidden”. SendGrid shows a new key only once, and a key can’t have more permissions than the user who creates it (Twilio SendGrid: API keys, checked October 2026).
- Permissions. Connecting needs
providers:manage; adding a new sending domain needsdomains:manage. - A public HTTPS address for the Event Webhook:
<public URL>/hooks/sendgrid/<token>. SendGrid has no events API that ReputeCast could poll instead, so the address must be reachable from the internet.
Connect SendGrid
Section titled “Connect SendGrid”-
Open Sending providers, choose Add provider and pick SendGrid in the catalog. Connect a sending provider explains the steps every provider shares.
-
Paste the API key. Set Region to
euonly for an EU subuser; otherwise keepglobal. Under the extra SendGrid settings you can name an IP pool of dedicated IPs to send through. Leave the Event Webhook verification key empty: ReputeCast reads it from SendGrid for the webhook it registers. -
Choose Connect. ReputeCast reads your credits and account with the key, then stores it encrypted.
-
In 2. Webhooks, ReputeCast tests its own public URL, then creates (or updates) an Event Webhook named “ReputeCast” for
delivered,bounce,dropped,deferred,spamreport,unsubscribeandgroup_unsubscribe, and turns on its signature verification. Processed, open and click events stay off. -
Choose Continue to domain verification and enter your sending domain. ReputeCast starts domain authentication in SendGrid (automated security) and lists the CNAME records SendGrid needs: the return path, SPF and two DKIM records. It also suggests a DMARC record if the domain has none.
-
In Test send, send a test and watch the
deliveredevent come back through the signed webhook. -
In Streams and Contacts, pick the streams and keep the option to pull SendGrid’s existing suppressions ticked.
Check that it worked
Section titled “Check that it worked”- The SendGrid card on Sending providers, then Providers shows Healthy, the plan’s credits and SendGrid’s reputation figure.
- In SendGrid › Settings › Mail Settings, the Event Webhook named “ReputeCast” points at
/hooks/sendgrid/…with signature verification on. - Deliveries and bounces appear under Sending providers, then Events & sync.
Each webhook request is signed with ECDSA over its timestamp and body; ReputeCast checks the signature with the public key SendGrid returns when signing is turned on (Twilio SendGrid: Event Webhook security features, checked October 2026). ReputeCast sends one API call per message, with click, open and subscription tracking off on each message whatever the account settings say. The suppression sync pulls SendGrid’s bounces, invalid emails, spam reports and global unsubscribes (not blocks) and pushes ReputeCast’s shared list to SendGrid’s global unsubscribes, which stops all mail to those addresses at SendGrid.
Troubleshooting
Section titled “Troubleshooting”- “SendGrid rejected this key.” The key is wrong or was deleted. Create a new key with Full Access and paste it.
- “SendGrid didn’t answer the check” right after you paste a valid key. SendGrid may be refusing because the account has used up its credits; ReputeCast treats that as a temporary limit. Check your plan, then try again.
- Webhook registration or the domain step fails with “access forbidden”. The key is restricted. Give it Full Access in SendGrid (or create a new one) and replace it under Settings, then Credentials.
- The test fails with
sender_not_verified. SendGrid sends only from a verified Sender Identity. Finish domain authentication for the From domain (or verify the single sender in SendGrid), then send another test. - Events stop and the card shows Degraded with Webhooks silent. The webhook was deleted, disabled or its signing turned off in SendGrid. Choose Re-register webhook on the provider’s incident; if you set up the webhook yourself, paste its verification key instead.
- Transactional messages with Cc, Bcc or attachments fail. The SendGrid adapter can’t send copies or attachments; route those templates through another provider.
- The catalog shows a “Sandbox mode” badge. ReputeCast never turns on SendGrid’s sandbox mode: every message it hands over is delivered.
- You changed the public URL or disconnected SendGrid. A new public URL adds a second Event Webhook; delete the old one in SendGrid. Disconnecting deletes the webhook at the current URL; authenticated domains, pushed suppressions and tracking settings stay.