delete/v2/webhook-endpoints/{id}

Delete an endpoint

Operation: deleteWebhookEndpoint
Authentication: API key

**Keeps its delivery history.** The endpoint is retired rather than removed: it stops being addressable and stops receiving, and `GET /v2/webhook-endpoints/{id}/deliveries` stays readable, because that log is the answer to the dispute this is usually part of.

Request

Parameters

idpathrequiredstring

Responses

204Deleted.

400The request body or query failed validation.

errorobjectrequired

401No key, an unknown key, a revoked key, or a key whose tenant is not active. All four return an identical body on purpose: distinguishing them would let a caller discover which partners we have.

errorobjectrequired

403The key is valid but lacks the scope, or it asked for a scope it does not itself hold.

errorobjectrequired

404Not found, or not yours. A resource belonging to another tenant answers 404 rather than 403, because 403 would confirm the record exists.

errorobjectrequired

Example

curl

curl -X DELETE https://api.haavisa.com/v2/webhook-endpoints/<id> \
  -H "Authorization: Bearer $HAAVISA_API_KEY"

More in Webhooks

Something unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.