Skip to content
HookDeploy
HookDeployDocumentation
On this page ↓
Getting startedIntroduction

What HookDeploy is, who it's for, and the core concepts behind webhook capture and replay.

→Getting startedQuickstart

From signup to your first captured webhook in under five minutes.

→Getting startedYour first endpoint

Create an endpoint, copy its URL, send test requests, and read the request inspector.

→Core conceptsForwarding

Forward captured webhooks to one or more destinations, with optional payload transformation.

→Core conceptsTransformations

Reshape webhook payloads before forwarding with the visual editor and 23 built-in formatters.

→Core conceptsEndpoint security

Restrict access to your HookDeploy endpoints with IP allowlists and secret token authentication.

→Core conceptsCustom Responses

Override the HTTP response HookDeploy returns to webhook senders. Set a custom status code, response body, and dynamic variables for testing and mocking.

→Core conceptsResponse Delay

Add an artificial delay before HookDeploy responds to a webhook sender. Useful for testing timeout handling and retry logic.

→
↑↓ navigateEnter openEsc close

Platform Verification

Automatically handle webhook verification handshakes from Meta, Slack, and Zoom so your endpoint registers without extra configuration.

Overview

Some platforms require a challenge-response handshake when you register a webhook URL. Without it, registration fails entirely. HookDeploy handles these handshakes automatically once you configure a preset — no separate server or custom code needed.

Plan availability

Platform verification is available on Starter, Team, and Enterprise plans.

Supported platforms

PlatformCoversMechanism
MetaFacebook, WhatsApp, Instagram, ThreadsGET request — echoes hub.challenge query param
SlackSlack appsPOST url_verification — echoes challenge field
ZoomZoom appsPOST endpoint.url_validation — HMAC-SHA256 response

Meta / Facebook / WhatsApp / Instagram

Meta sends a GET request with hub.mode, hub.verify_token, and hub.challenge query params. HookDeploy checks that hub.verify_token matches your configured token and echoes back hub.challenge as plain text.

Setup: select the Meta preset on the Security tab, enter any string as your verify token, then enter the same string in Meta’s webhook settings.

Slack

Slack sends a POST with {"type":"url_verification","challenge":"..."}. HookDeploy responds with {"challenge":"<value>"} automatically. No additional configuration needed beyond selecting the Slack preset.

Zoom

Zoom sends a POST with {"event":"endpoint.url_validation","payload":{"plainToken":"..."}}. HookDeploy computes an HMAC-SHA256 hash of the plainToken using your Zoom Secret Token and responds with both values.

Setup: select the Zoom preset, enter your Zoom Secret Token (found in your Zoom app’s Event Subscriptions settings). The secret is encrypted and stored securely — it is never returned to the dashboard after saving.

How verification and custom responses coexist

Verification challenges are intercepted before normal capture logic. They are not recorded as requests, do not count toward usage, and do not trigger forwarding or subscriptions. Your custom response config applies only to normal webhook traffic — not to verification handshakes.