Send SendGrid events back to your suppression list

Point the SendGrid Event Webhook at your workspace. Bounces, spam reports, and unsubscribes update your suppression list.

Get started free Delivery feedback

Fig. 1SendGrid → Verifier

1.1 SendGrid

SendGridEvent Webhook

1.2 Delivery endpoint

Token in the URL
Signed webhook, public key
Timestamp window

1.3 Recorded as

delivered → deliveredHistory
bounce → bouncedSuppressed
spamreport → complainedSuppressed
unsubscribe → unsubscribedSuppressed
open → openedHistory
click → clickedHistory

POST /v1/inbound/providers/sendgrid/{endpoint}/{token}

Source: SendGrid Event Webhook
Verification: Signed webhook and timestamp
Suppressed: Bounces, spam reports, unsubscribes
Setup: One private URL

§ 1

Why it matters

Delivery problems stay inside SendGrid

When an event is only recorded in the email platform, the address comes back with the next import.

Close the loop between SendGrid and your list checks.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Bounces and spam reports stay in SendGrid.With Verifier: Each SendGrid event is checked for a valid signature.
Without: Imports from other tools bring the same addresses back.With Verifier: Bounces, spam reports, and unsubscribes join one suppression list.
Without: Suppression lists differ from tool to tool.With Verifier: Every event shows in the address history.

§ 2

How it works

A private URL for each endpoint

Turn on the signed Event Webhook in SendGrid. Verifier checks each request with your SendGrid verification key and a timestamp window.

2.1In SendGrid, open Settings > Mail Settings > Event Webhooks, and turn on signature verification. Copy the verification key.
2.2In Verifier, open Outcomes, and add a SendGrid endpoint with that key. Copy its private URL.
2.3In SendGrid, paste the URL as the Post URL. Select the bounce, spam report, and unsubscribe events.

Fig. 3One bounce from SendGrid

Sent by SendGrid

[  {    "email": "[email protected]",    "event": "bounce",    "type": "bounce",    "reason": "550 5.1.1 User unknown",    "timestamp": 1760605964,    "sg_event_id": "ZGVsaXZlcmVkLTA..."  }]

Verifier · POST /v1/inbound/providers/sendgrid/{endpoint}/{token}

{  "provider": "sendgrid",  "accepted": 1,  "duplicates": 0,  "rejected": 0}

GET /v1/suppressions/[email protected]

{  "suppressed": true,  "reason": "bounce",  "source": "sendgrid"}

Signed with your SendGrid verification key · fields trimmed

§ 3

What you get

What you get.

3.1One suppression listSuppressions from SendGrid sit next to invalid results and manual entries.
3.2Event historySee the delivery events for each address in its history.

Table 3 · Event mapping

Event from the platform	Recorded as
delivered	delivered
bounce	bounced
spamreport	complained
unsubscribe	unsubscribed
open	opened
click	clicked

§ 4

In practice

Typical uses.

Case 4.1
Stop repeat problems
A suppressed address goes to the drop file when you clean your next list.
Case 4.2
More than one sending tool
A SendGrid bounce also stops the address in lists from your CRM and other tools.

Other integrations.

All integrations

Questions

Before you start.

Which events are recorded?

The event mapping on this page shows what is recorded. Bounces, spam reports, and unsubscribes go on the suppression list.

How do you know an event came from SendGrid?

SendGrid signs each request. Verifier checks the signature with the verification key that you added to the endpoint. A request with a bad signature or an old timestamp is rejected.

Delivery problems stay inside SendGrid

When an event is only recorded in the email platform, the address comes back with the next import.

Close the loop between SendGrid and your list checks.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Bounces and spam reports stay in SendGrid.With Verifier: Each SendGrid event is checked for a valid signature.
Without: Imports from other tools bring the same addresses back.With Verifier: Bounces, spam reports, and unsubscribes join one suppression list.
Without: Suppression lists differ from tool to tool.With Verifier: Every event shows in the address history.

A private URL for each endpoint

Turn on the signed Event Webhook in SendGrid. Verifier checks each request with your SendGrid verification key and a timestamp window.

2.1In SendGrid, open Settings > Mail Settings > Event Webhooks, and turn on signature verification. Copy the verification key.
2.2In Verifier, open Outcomes, and add a SendGrid endpoint with that key. Copy its private URL.
2.3In SendGrid, paste the URL as the Post URL. Select the bounce, spam report, and unsubscribe events.

Fig. 3One bounce from SendGrid

Sent by SendGrid

[  {    "email": "[email protected]",    "event": "bounce",    "type": "bounce",    "reason": "550 5.1.1 User unknown",    "timestamp": 1760605964,    "sg_event_id": "ZGVsaXZlcmVkLTA..."  }]

Verifier · POST /v1/inbound/providers/sendgrid/{endpoint}/{token}

{  "provider": "sendgrid",  "accepted": 1,  "duplicates": 0,  "rejected": 0}

GET /v1/suppressions/[email protected]

{  "suppressed": true,  "reason": "bounce",  "source": "sendgrid"}

Signed with your SendGrid verification key · fields trimmed

What you get.

3.1One suppression listSuppressions from SendGrid sit next to invalid results and manual entries.

3.2Event historySee the delivery events for each address in its history.

Table 3 · Event mapping

Event from the platform	Recorded as
delivered	delivered
bounce	bounced
spamreport	complained
unsubscribe	unsubscribed
open	opened
click	clicked

From a raw listto a safe send.

Send SendGrid events back to your suppression list

Delivery problems stay inside SendGrid

A private URL for each endpoint

What you get.

Typical uses.

Other integrations.

Before you start.

From a raw listto a safe send.

Send SendGrid events back to your suppression list

Delivery problems stay inside SendGrid

A private URL for each endpoint

What you get.

Typical uses.

Other integrations.

Before you start.