Integrations

SendGrid Webhooks Guide

SendGrid Event Webhooks report email delivery, engagement, bounce, unsubscribe, and spam events. These streams often feed analytics, compliance, customer success, and support systems, so failed delivery can hide important customer communication signals.

FastHook receives signed SendGrid Event Webhook traffic, verifies the configured public key, preserves the raw request, routes event families to destinations, and lets operators retry or replay failed email event windows.

Provider event routing topology for email event webhooks.
SendGrid engagement, bounce, and compliance events usually belong to different downstream workflows.

SendGrid signature headers

  • x-twilio-email-event-webhook-signature: ECDSA signature.
  • x-twilio-email-event-webhook-timestamp: timestamp prepended to the raw body before verification.

Create a SendGrid source

Create SendGrid source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "SendGrid production",
    "type": "SENDGRID",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "SENDGRID",
        "public_key": "-----BEGIN PUBLIC KEY-----..."
      },
      "allowed_http_methods": ["POST", "PUT", "PATCH", "DELETE"]
    }
  }'

Routing strategy

  • Route bounce and dropped events to deliverability or support destinations.
  • Route open and click events to analytics destinations with rate limits.
  • Route unsubscribe and spam report events to compliance workflows.
  • Use replay carefully for engagement events because high-volume windows can be noisy.

Related guides