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, 35 built-in formatters, conditions, and form-encoded support.

→Core conceptsPrivacy filters

Reshape or redact webhook payloads before HookDeploy stores them ΓÇö without changing what forward destinations receive.

→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 conceptsEndpoint security

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

→
↑↓ navigateEnter openEsc close

Private Delivery

Starter+

Deliver captured webhooks to private services with the HookDeploy Agent dialing out over mTLS, without exposing a handler to the public internet.

Private delivery sends captured webhooks to a loopback port and path on a machine you control. The source-available HookDeploy Agent dials out over mTLS, stays connected, and receives traffic destined for it — no public IP, no open inbound port.

Private delivery vs public HTTPS

Standard forwarding delivers to a public https:// URL. Private delivery instead targets an enrolled agent: HookDeploy pushes the webhook through a regional relay; the agent forwards it to 127.0.0.1 on the port and path you configure.

Both destination types use the normal HookDeploy forwarding workflow: configure a destination, receive per-attempt status in request details, and use the destination’s retry controls. Standard public HTTPS forwards use a 15-second delivery timeout.

Customer setup

  1. Install the CLI on Linux, or install the Desktop Agent on Windows or macOS.
  2. Enroll the machine into your organization from the dashboard (enrollment token or browser login) and keep the agent connected — see the Agent overview.
  3. In the HookDeploy dashboard, open the endpoint’s forwarding settings and add an agent forward destination: select the enrolled agent, loopback port, and path.
  4. Confirm your local handler is listening on that port and test the destination before relying on it for production traffic.

Keep your enrolled agent and local handler secured, and grant only the access required for webhook delivery. HookDeploy support can help validate configuration, but you remain responsible for the enrolled device and the service listening on loopback.

Availability and pricing

Private delivery uses production agents. Free includes 0 production agents. Starter includes 1, Pro includes 2, Scale includes 5, and Enterprise includes 10. Extra production agents are $9 per month on Pro and Scale only; Enterprise has no overage path.

Development agents are unlimited on every plan, including Free, with fail-fast (no-retry) delivery — separate from production-agent limits. See Production vs Development for environment behavior.

Next steps

  • Forwarding — Destination behavior, retries, and result tracking
  • Endpoint security — Stored payload protection and organization isolation