Webhook Testing

Request Bin

A request bin is a temporary webhook inbox. Create a URL, send a request to it, inspect the method, path, headers, query string, and body, then delete the inbox when the test is done.

FastHook request bins are built on the same source and request pipeline as production FastHook flows. That means a quick test can become a real routed webhook workflow when you are ready.

Open request binsCompare Webhook.site alternative

When to use a request bin

  • Testing whether a provider sends the webhook at all.
  • Inspecting headers, payload shape, content type, and query parameters.
  • Sharing a sanitized request with another developer or support teammate.
  • Checking webhook behavior before creating destinations, filters, or transformations.
  • Running quick cURL experiments without setting up a full flow.

Request bin vs production source

CapabilityRequest binProduction source
SetupOne click, temporary URL.Named source with auth and routing setup.
LifetimeExpires automatically after the selected TTL.Stays active until disabled or deleted.
DestinationsNot required for capture and inspection.Routes to HTTP, CLI, Slack, Sheets, S3, R2, email, Telegram, and more.
Best forFast debugging, demos, and payload discovery.Operational delivery, retries, replay, transformations, and recovery.

How to create a request bin

  1. Open the FastHook dashboard and go to Bins.
  2. Choose a TTL: one hour, 24 hours, or seven days.
  3. Create the bin and copy the generated webhook URL.
  4. Send a request from cURL, a provider dashboard, or your application.
  5. Inspect the request live, including headers and body.
  6. Copy a sanitized request when you need to share evidence safely.

Example cURL request

curl -X POST "https://hook-xxxxxx.fasthook.io/" \
  -H "Content-Type: application/json" \
  -H "X-Event-Type: order.created" \
  -d '{
    "id": "evt_test_001",
    "type": "order.created",
    "customer": {
      "email": "dev@example.com"
    }
  }'

What FastHook captures

  • HTTP method, path, query string, and timestamp.
  • Headers, including content type and provider metadata.
  • Raw or parsed request body where available.
  • Accepted or rejected request status.
  • Request history for the temporary bin until normal retention cleanup.

Automatic cleanup

Request bins are intentionally temporary. Expired bin sources are cleaned up automatically by FastHook's daily cleanup job, and the ingress layer rejects expired bin URLs with a gone response. This keeps test URLs from becoming forgotten public endpoints.

From request bin to webhook flow

Once the payload shape is known, create a full FastHook source for the provider and add the routing pieces you need: filters, transformations, destinations, retries, replay, and rate limits. A request bin is the fast discovery step; a FastHook flow is the reliable delivery path.

Related resources