All documentation

Hooks · Customer documentation

Receive, inspect, and replay webhooks from external services.

What you prepare

A service that can send webhooks; no receiving server needed.

Steps in the workspace

  1. 01Create an inbox and copy its URL.
  2. 02Register it with the sender and trigger a test event.
  3. 03Inspect the event and replay it if needed.

Example request / integration

Point a test payment webhook to the inbox, inspect its JSON, then replay after fixing your handler.

# After creating an inbox, copy its receiving URL.
curl -i -X POST "$INBOX_URL" \
  -H 'Content-Type: application/json' \
  --data '{"event":"payment.test","orderId":"sample-123"}'
# Return to the workspace and open Received events.

Examples use placeholders: replace $BASE_URL, $SESSION_TOKEN and issued URLs with real values. Never publish session tokens or API keys in a webpage or repository.

Management API entry point

POST /api/picosvc/hooks/inboxes

Inbox name; register the resulting URL with your webhook sender.

Receiving URL, event history, headers, body, and replay result.

What it does not do

It does not perform sender-signature verification or replace your production handler.

Feature comparison and sources

Captured-request workflowInbox-based capture, history, and replay to a URL.

Webhook.siteDocuments APIs to list and inspect captured requests.

Feature comparison and sources · Webhook.site
Overview, workspace, and dashboard

The product overview is public. The workspace handles creation, editing and history. The all-service dashboard shows usage and links for all 16 tools.