socket.help

Request forwarding

Capture requests and forward them to another endpoint.

Your next request starts here.

Create an endpoint, send it a webhook, and see the headers, body, and query parameters as they arrive.

Receiving is public by default. Inspection and captured data stay private. Private receiving requires X-Access-Token from senders.

Free · Expires after 1 hour · No account needed
Open an existing inbox

Private to inspect. Expires after one hour. API reference

About Request forwarding

Capture a webhook in your workspace and relay it to a public HTTP endpoint. Pro and Team only.

When to use it

Inspect a webhook while your own public development endpoint receives the same request. Pro and Team only.

Request forwarding example
Create an owned webhook inbox, then:
PUT /api/inboxes/{id}/forward
{"url":"https://your-app.example/hook"}

Inspect /api/inboxes/{id}/deliveries for attempts and status.

How to use it

  1. Create a webhook inbox while signed in.
  2. Configure its forwarding URL through the inbox API or CLI.
  3. Inspect delivery attempts and captured payloads.

Limits & privacy

Requires an active Pro or Team subscription and an owned inbox. Targets must be public HTTP(S), with redirects and private networks blocked. Forwarding pauses immediately when the subscription lapses. Binary bodies are not forwarded; see the webhook forwarding API for retry limits.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.