`api_request_failures`

Debug the partner API — recent failed requests and why.

Authentication required

Endpoint

endpoint

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

When to use it

When a partner integration reports errors and you want the server’s side of the story.
To find which credential a failing call was made with.

Parameters

limitnumberoptional

Max failures (default 20).

Returns

Recent failed API-client requests, newest first, with the operation name, error messages and codes, and the credential used.

Example

POST this to the endpoint above.

JSON-RPC

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

content

2 failure(s):
- CreateRegistration · FORBIDDEN ·
  "Insufficient scope" · api key "Front desk"

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.

api_request_failures

Debug the partner Business API: recent failed API-client requests (API-key or OAuth calls whose GraphQL execution returned errors), newest first, with the operation name, error messages and codes, the credential that made the call, and the request id for support correlation. Rows are kept for roughly 30 days.