delete_webhook_endpoint
Remove an outbound webhook endpoint. Destructive — an integration listening on it goes dark at once; its delivery log is kept.
Purpose
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.
Required ability
webhook-endpoint:delete
Input schema
{
"type": "object",
"required": ["endpoint_id"],
"properties": {
"endpoint_id": {
"type": "string",
"description": "UUID of the webhook endpoint to remove."
}
}
}Output shape
{
"data": {
"endpoint_id": "c62a08f4-1b7d-4e35-9860-a37f5d21e0b9",
"deleted": true
}
}Example prompts
"Delete webhook endpoint
c62a08f4-1b7d-4e35-9860-a37f5d21e0b9— the CRM was decommissioned." (confirm first)
"Remove the old staging endpoint from the team."
"We're replacing the hooks URL; delete the current endpoint after the new one is registered."
Failure modes
FORBIDDEN— the token belongs to a team member who did not register the endpoint and is not the team owner.VALIDATION_FAILED— the removal was refused for the endpoint's current state.RESOURCE_NOT_FOUND— unknown or already-deletedendpoint_id, or an endpoint of another team.AUTHENTICATION_REQUIRED— no authenticated user on the request.TOKEN_MISSING_ABILITY— token lackswebhook-endpoint:delete.
Related
pause_webhook_endpoint— the reversible alternative.list_webhook_endpoints— what is left.- Webhook endpoints API — the REST equivalent, a
204.
How is this guide?