Webhook Endpoints

Create and copy an endpoint

Use a webhook endpoint when a sender needs a public destination and you want to inspect its HTTP request without exposing a local server.

1. Select Start debugging.
2. Wait for the workspace to open, then copy Webhook URL.
3. Paste the receiving URL into your sender. Keep its original token unchanged.

Each endpoint has its own captured requests and custom response. Creating another endpoint does not move traffic from the old address.

Receiving and workspace URLs

The public receiving URL accepts deliveries. The workspace URL opens the inspector in your browser. Copy Webhook URL in the workspace for your sender; do not send to the browser address. A receiving token or workspace UUID alone does not grant history or management access.

You may append subpaths such as /orders and query parameters to the receiving URL. These remain captures for the same endpoint, not separate routes with different responses.

For a complete synthetic send, use the Quickstart cURL example.

Guest and account access

Guests can create endpoints and send requests without signing in. Return using the original browser with valid guest management access; clearing browser storage or losing the session can remove that access.

Account endpoints require the owning account. Signing in can claim eligible guest endpoints; it does not transfer another user’s endpoints or guarantee every guest endpoint will fit within account limits. Keep management credentials private.

Send test request requires both sign-in and endpoint access. External senders use only the receiving URL.

Endpoint lifetime

Check the expiration time and timezone in the workspace. Account endpoints are temporary too. Expiration stops receipt and history access; it cannot be undone.

Before expiry, a signed-in owner may explicitly extend an eligible endpoint in Settings. See extension behavior and current limits. A replacement endpoint has a new receiving URL, so update every sender.