---
title: "Call the getWebhookEndpoints MCP tool"
method: POST
path: "/api/v1/actions/getWebhookEndpoints"
tags: ["Actions"]
---

# Call the getWebhookEndpoints MCP tool

`POST /api/v1/actions/getWebhookEndpoints`

## Request

- Base URL: `https://app.reachium.io`
- URL: `https://app.reachium.io/api/v1/actions/getWebhookEndpoints`
- Auth: HTTP bearer

List the workspace's outbound webhook endpoints, or read one endpoint's recent delivery attempts. Default view "endpoints" lists all configured endpoints (id, url, events, is_active, consecutive_failures); pass endpoint_id to see just that one. View "deliveries" (requires endpoint_id) returns that endpoint's recent delivery attempts newest first, with next_cursor for paging further back. The signing secret is never returned here. From this surface a secret is viewed or rotated only in Settings > Developer > Webhooks in Reachium; never ask the user to paste a secret into chat. The REST API returns the secret once, at creation or rotation, for server-side automation.

Called through the Actions bridge: the response is that tool's own result, wrapped as `{ data: <tool result> }` under HTTP 200. Billing, daily-cap, and confirm-step outcomes are embedded INSIDE `data`, never remapped to an HTTP status (see the templated `/api/v1/actions/{toolName}` operation above for the full protocol, and `x-mcp-actions` for this tool's machine-readable scope/cap/confirm_behavior fields). Authentication, request-shape, and optional idempotency-protocol failures still use their documented non-200 statuses.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `endpoint_id` string, uuid: Restrict to one endpoint. Required when view is "deliveries".
  - `view` 'endpoints' | 'deliveries': "endpoints" (default) lists configured endpoints; "deliveries" reads one endpoint's recent delivery attempts.

## Response `200`

The result of calling this tool.

- object
  - `data` unknown, required
  - `error` unknown, required

## Other responses

- `400`: The request body was not a JSON object (code invalid_request), or Idempotency-Key is malformed (code invalid_idempotency_key).
- `401`: Missing or invalid API key. Send `Authorization: Bearer rmcp_...` (code unauthorized).
- `403`: This tool is out of the key’s granted scope (code insufficient_scope).
- `409`: This Idempotency-Key has an unresolved in-flight or ambiguous result (code request_in_flight). Reconcile before using a new key.
- `422`: This Idempotency-Key was already used with a different request body (code idempotency_key_reuse).
- `429`: Rate limited: shared `mcp:ip:{ip}` (600/60s) or `mcp:key:{keyId}` (120/60s) bucket, the SAME buckets the MCP endpoint uses (code rate_limited).
- `500`: Unhandled server error (code internal_error).

---

[API](https://skmtc.dev/reachium/apis/reachium-api.md) · [All operations](https://skmtc.dev/reachium/apis/reachium-api/llms.txt) · [OpenAPI document](https://skmtc.dev/reachium/apis/reachium-api/revisions/11682826692b?raw)