`webhook_deliveries`

Debug webhook delivery — recent attempts, failures and retries.

Authentication required

Endpoint

endpoint

https://business.sessions.website/@<handle>/api/mcp

When to use it

The first stop when a business says "we stopped getting webhooks".
To tell a transport failure from a 4xx the receiving endpoint returned.

Parameters

endpointstringoptional

Webhook endpoint id (optional; defaults to all endpoints).

statusstringoptional

Only show deliveries with this status: pending, succeeded, failed, or deadLettered (optional).

limitnumberoptional

Max deliveries fetched per endpoint (default 20).

Returns

Recent delivery attempts with status (pending, succeeded, failed, deadLettered), attempt count, HTTP response code, failure reason and retry schedule.

Example

POST this to the endpoint above.

JSON-RPC

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "webhook_deliveries",
    "arguments": {
      "status": "failed",
      "limit": 20
    }
  }
}

content

3 delivery(ies):
- registration.created → 500 · failed ·
  attempt 3/5 · retry at 2026-09-02T10:14

What the agent is told

The description the model reads when deciding whether to call this. It is the only thing that decides whether the tool fires at the right moment, so it is worth knowing what it says.

webhook_deliveries

Debug webhook delivery: recent delivery attempts with status (pending / succeeded / failed / deadLettered), attempt count, HTTP response code, failure reason, and retry schedule. Optionally scope to one endpoint id and/or filter by status (the status filter is applied to the most recent deliveries fetched).