Version
READ

get_webhook_endpoint

One of the team's outbound webhook endpoints by UUID, with its health counters. The signing secret is never returned.

Read one endpoint back: its target, the events it receives, whether it is active, and the health counters the dashboard shows — total failures, the current consecutive-failure streak and the last success and failure instants. The row is the one list_webhook_endpoints returns.

Never the secret

The signing secret exists in the create_webhook_endpoint and rotate_webhook_endpoint_secret responses only. If a consumer has lost it, rotate.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Read-only

It reads and never changes anything.

Arguments

endpoint_id*string

UUID of the webhook endpoint to fetch.

What it returns

{  "data": {    "id": "c62a08f4-1b7d-4e35-9860-a37f5d21e0b9",    "name": "CRM sync",    "url": "https://hooks.example.com/subscriby",    "project_id": null,    "events": ["subscription.created", "subscription.cancelled"],    "is_active": true,    "disabled_at": null,    "allowed_ips": [],    "failure_count": 2,    "consecutive_failures": 0,    "last_success_at": "2026-09-05T18:00:00+00:00",    "last_failure_at": "2026-08-30T07:12:00+00:00",    "created_at": "2026-05-18T10:05:00+00:00"  }}

consecutive_failures is the streak that disables an endpoint when it runs too long; failure_count is the lifetime total. disabled_at is set when the endpoint is paused, by a person or by the streak.

How it fails

RESOURCE_NOT_FOUND

unknown endpoint_id, or an endpoint of another team.

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks webhook-endpoint:view.

How is this guide?

Last updated on