Skip to main content
Question

About Webhook Signatures and/or Headers

  • July 5, 2026
  • 1 reply
  • 55 views
P

Hey AC,

just a heads up that your Webhook UI (the one under Settings > Developers > Webhooks) offers a way to define Signature and other Headers. When entered and saved, the signature/headers is shown again while editing the same webhook (so it seems they are correctly saved along the other webhook data).

BUT: neither signature (which itself is also just a header with redacted value field) nor the other public headers are sent along. Not while sending test data, nor when receiving real triggered data.

Please fix this bug asap or remove the UI that suggests the feature is available.

PS: If it helps, the webhook in question is an unsubscribe webhook with contact, user and system initiated sources.

1 reply

Alanna Hurley
Forum|alt.badge.img+3
  • Alanna Hurley
  • Community Manager
  • July 7, 2026

Thanks for flagging this!

If the UI allows Signature and custom headers to be added and saved, it’s reasonable to expect those values to be sent with both test payloads and real webhook events. I can see why that would be frustrating, especially if the settings appear to save correctly but never make it into the request.

I can’t confirm the root cause from the community side, but this does sound like something our Support team should investigate as a potential bug. I’d recommend opening a support ticket and including the details you shared here, especially:

  • that this is happening on an unsubscribe webhook

  • that the configured signature and other headers are not being sent

  • that it happens on both test sends and real triggered events

  • that you’ve seen it with contact-, user-, and system-initiated unsubscribe sources

If you’re able to include a captured request showing the missing headers, that should help the team investigate faster.

Thanks again for calling this out so clearly!

Terms & ConditionsAccessibility statement