What is Hookdeck?
Hookdeck sits between a webhook producer and the application that consumes the event. A provider sends a request to a Hookdeck Source URL, Hookdeck records it as an event, and connection rules route it to one or more destinations. Filters, transformations, rate limits, and delays can change what reaches each destination, so a Hookdeck request in server logs may differ from the provider's original delivery.
There are two authentication boundaries. A Source can verify the original provider with a supported signature scheme, Basic authentication, or an API key. When that check succeeds, Hookdeck adds x-hookdeck-verified: true. Hookdeck then signs the event it forwards to a destination with the project signing secret by default.
The destination signature is a base64-encoded HMAC SHA-256 value in x-hookdeck-signature. During a delayed secret rotation, Hookdeck can also send x-hookdeck-signature-2. Failed destination attempts can be retried according to the connection's policy, and Hookdeck records each response for later inspection or manual retry.
Hookdeck transports configured application events rather than public web content. The traffic has no role in AI search or model training. Robots.txt cannot govern a Source URL or destination callback because neither request is a web crawl.
