Lists the catch URLs (endpoints) in the current SlingHook workspace, with where each one relays events. Start here to find the endpoint a webhook was sent to.

Lists webhooks captured on an endpoint, newest first, as short summaries (number, time, method, event type, signature status) without bodies. Use get_event for one event in full. Without query or before_id it reads the newest events (up to 50, every plan). query and before_id search the whole retained history, which needs the Pro plan.

Reads one captured webhook in full: method, headers, query string, body and signature status. Long bodies are cut at max_body_chars.

Explains why a webhook's signature verified or failed: detected provider scheme (Stripe, GitHub, Shopify, Slack, Standard Webhooks, Twilio), wrong secret, stale timestamp, or a body that was modified (reformatted JSON, re-escaped slashes). Checks against the secret saved on the endpoint, or against secret to try a candidate without saving it.

Re-sends a captured webhook to a URL from this machine (e.g. the local handler at http://localhost:3000/webhooks), with its original method, headers and body, so signature checks run for real. Records the result in the dashboard's replay history and returns the verdict against the previous attempt to the same URL: fixed, regressed, still_failing or still_passing. For an event whose signature is invalid, the handler passes by rejecting it (4xx). It can change state in the receiving app (it is a real webhook delivery).

Shows the replay history of one event and the fix verification verdict for the latest replay (or replay_id): fixed, regressed, still_failing or still_passing, compared with the attempt before it to the same URL. Includes replays made from the dashboard and by slinghook listen. On Pro and above it also returns both response bodies to compare.

Lists the saved scenarios on an endpoint: ordered sets of captured events (for example subscription created, payment failed, canceled) that run_scenario replays in sequence. Scenarios are built in the dashboard.

Replays every event of a saved scenario, in order, from this machine to a URL (e.g. the local handler), and reports each step: status, pass or fail, and the verdict against that event's previous replay to the same URL. Use it after a fix to prove a whole flow works, not just one event. Steps go back to back unless keep_timing is set (gaps capped at 5 seconds). Each step is a real webhook delivery recorded in replay history, so it can change state in the receiving app.

Turns a real captured webhook into code to build a handler around: typed models of its payload, a fixture file with the body, and a test that posts it to the handler. Languages: typescript (types + Jest/Vitest test), python (dataclasses + pytest), php (DTO + Laravel test), go (structs; no test). Returns file contents with suggested names; it writes nothing, so save them with your own file tools. Also says which signature scheme the endpoint checks, so the handler can verify it.

Shows what differs between two captured webhooks, field by field (JSON paths such as data.items[0].price), plus header differences. Use it for "this one worked and that one failed, what changed?" or to spot a provider changing its payload. Leave out b to compare with the previous event of the same type on the same endpoint. Changes always read from the older event to the newer one. Key order, formatting and per-delivery headers (signatures, request ids, dates) never count.

Creates a new catch URL (endpoint) in the current workspace and returns the URL to paste into the provider's webhook settings. If an endpoint with the same name already exists, returns that one instead of making a copy. Plan limits apply (Free has 3 endpoints). It does not take a signing secret: secrets are added in the dashboard so they never pass through the conversation.