delete_webhook_endpoint
Remove an outbound webhook endpoint. Destructive — an integration listening on it goes dark at once; its delivery log is kept.
Remove an endpoint the team no longer wants. Deliveries to it stop immediately and its delivery log
is kept for reference. If the intent is "stop it for now",
pause_webhook_endpoint does that reversibly and keeps the
secret.
Destructive — confirm the endpoint with a human first
Whatever is listening on the URL stops receiving events with no notice.
Confirm the exact endpoint_id with the creator before calling.
Only the creator who registered the endpoint, or the team owner, may remove it; a fellow team member
is refused with FORBIDDEN. Idempotent: an already-deleted id surfaces as RESOURCE_NOT_FOUND,
exactly as an unknown or foreign id does.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time.
Arguments
endpoint_id*stringUUID of the webhook endpoint to remove.
What it returns
{ "data": { "endpoint_id": "c62a08f4-1b7d-4e35-9860-a37f5d21e0b9", "deleted": true }}How it fails
FORBIDDENthe token belongs to a team member who did not register the endpoint and is not the team owner.
VALIDATION_FAILEDthe removal was refused for the endpoint's current state.
RESOURCE_NOT_FOUNDunknown or already-deleted endpoint_id, or an endpoint of another team.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks webhook-endpoint:delete.
How is this guide?
Last updated on