Integration · Custom HMAC
Custom HMAC webhook gateway
Need to ferry webhooks from a provider Charon doesn't natively support? The generic provider type accepts any HMAC-signed webhook (X-Charon-Signature, X-Webhook-Signature, X-Signature) and the same DLQ, retry, and replay machinery applies — no custom code needed.
Why Charon Gate for Custom HMAC
- Bring-your-own-secret HMAC verification — works with any system that signs the body with HMAC-SHA256.
- Skip verification for unsigned legacy webhooks (audit-logged so you know which events were not verified).
- Same retention, redaction, and replay semantics as the first-party providers.
How verification works
- Header
- X-Charon-Signature (or X-Webhook-Signature / X-Signature)
- Algorithm
- HMAC-SHA256 of the raw body, hex-encoded with optional `sha256=` prefix
- Upstream docs
- /docs
Example Custom HMAC events
Charon Gate is event-shape agnostic — these are typical Custom HMAC event types our customers route through us today.
custom.event.createdcustom.event.deletedFAQ
- Can I add a new first-class provider?
- Open an issue with the provider's signing details and we'll prioritise it. Until then, the generic provider gets you 90% of the value.
Ready when you are
Front your Custom HMAC webhooks with Charon Gate in 90 seconds.