Step One - Initial Testing
Hookdeck is a fully-featured end-to-end webhook management platform. Designed to be an all-in-one solution, Hookdeck unifies a wide variety of webhook functionality in a fast and flexible interface, allowing you to spend more time on your product's features and less on developing and maintaining common infrastructure.
Signing Up
Hookdeck is a hosted solution, so there's no installation process. All you need is a free account to get started!
We support authentication by email or SSO with Google and GitHub.
Complete the sign-up form at dashboard.hookdeck.com/signup.
Give your workspace a name and click Create Workspace
Creating a Connection
Creating a connection will allow you to start routing webhooks with Hookdeck by connecting a Source to one or more Destinations.
Once you create your first workspace, the onboarding process should guide you through creating your first connection. If for any reason you missed this page, access it here before following the steps below.
Give your source a name under Set your first source.
Give your destination a name under Set your first destination.
- If you have a live server, enter the HTTP URL.
- If you wish to receive on your localhost, enter the path.
- If you don't have a destination server ready to receive requests, you can use Hookdeck's Mock API.
Our Mock API is a live server that will always return an HTTP 200 status, allowing you to inspect the data your server would be receiving.
Define any rules you'd like your first connection to adhere to.
Click Create Connection
Next, let's verify the connection to make sure everything's working properly.
Receiving a webhook
Verifying the connection lets you know Hookdeck is properly ingesting and processing webhooks from your source.
- Copy the provided Hookdeck URL and paste it into your API provider's webhook URL field.
- Test the connection by triggering a webhook on your source. If you don't want to trigger a webhook at this time, you can skip this step.
- Click Go to Dashboard.
As soon as Hookdeck receives your first webhook, you'll see it appear in the Requests and Events lists.
A request is the webhook received from the third-party application to Hookdeck. Learn more about requests here
An event is the webhook delivered from Hookdeck to your destination. In many cases, the event will differ from the request after applying configurable post-processing as the data passes through Hookdeck. Learn more about events here.
Inspecting the data
After receiving data in the dashboard, you will see logs in Requests and Events.
Click the event you wish to inspect. You can see all the relevant metadata, including the headers, body, and server response for each webhook attempt.
Replaying a webhook
Once an event is in Hookdeck, retry the event to re-trigger your workflow as many times as needed to build your integration. Learn more about event retries here.
Up Next
You are now receiving webhooks and replaying them to test your use case! Next, we'll dig in to some more advanced configuration of your connections.