Introduction

What's Hookdeck?

Hookdeck is a development and production service that provides developers with all the tooling they need to monitor and troubleshoot webhook events. Benefiting from stable and reliable ingestion and delivery of large volume of webhook.

What's a webhook infrastructure?

When dealing with a large volume of webhooks, the best practices recommend that you build and implement a webhook ingestion infrastructure. The idea of this infrastructure is to delay the processing of webhooks to a later point in time through the use of queues. The reason behind this is to be able to handle large spikes in webhooks since you do not have control of the rate at which you receive webhooks and their content.

A typical infrastructure will feature an ingestion service (AWS Lamba, Cloud Run, etc.), file storage (S3, Cloud Storage, etc.), a queue (SQS, PubSub, RambitMQ, etc.), a set of workers, a monitoring tool, and a scheduler. Hookdeck, on its own, implements all these services into a single product that's plug and play. Hookdeck has built-in support for throttling delivery, storing payloads, handling a large volume of webhook events, retrying webhook events, and alerting logic amongst other things.

We would recommend taking action directly on webhooks received through Hookdeck instead of queuing the message as you would otherwise. Hookdeck implements all the logic you need to safely handle webhooks and recover from errors. You do not need to build any additional infrastructure.

Hookdeck empowers you to monitor and troubleshoot webhooks from any API Provider. This is a much less complex approach compared to building a custom solution to handle webhooks for each API provider.

How does Hookdeck work?

Hookdeck works by proxying your webhooks through our own infrastructure. You can now focus on providing more value for your customers instead of maintaining a custom backend infrastructure.

Webhook connections are defined by their Source, Destination and Ruleset.

• A Source represent an API sending you a webhook, such as Shopify, Stripe, Github, etc. Each source is assigned a unique Webhook URL that can be provided to the sender.

• A Destination represents an endpoint on your own server. Hookdeck will be forwarding all webhooks received to that URL with an HTTP POST request containing the original data from the sender along with additional Hookdeck metadata.

• A Ruleset is a reusable component across your connection to specify what retry logic and alerting logic to apply to your webhook connection.

Hookdeck will ingest any HTTP POST request to your Source Webhook URL and forward them to your destination URL.

Why use Hookdeck?

Requirement

Hookdeck has no external dependencies. If your system can receive HTTP POST requests, you’re ready to go.