Delete partner's webhook

Delete Partner's Webhook

This endpoint permanently removes a specific webhook from a partner's configuration. Once deleted, the webhook will stop receiving notifications for its associated event type. Deletion is irreversible — if the webhook is needed again, it must be recreated.

Endpoint

DELETE /api/Partners/webhooks/{id}

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a partner needs to decommission a webhook that is no longer needed — for example, when retiring a test configuration, replacing an endpoint with a new URL, or removing webhook delivery for security or maintenance reasons. Partners should confirm their systems no longer depend on the webhook before deleting it.

Path Parameters

ParameterTypeRequiredDescription
idinteger (int32)YesThe unique identifier of the webhook to be deleted

Response

200 OK

The webhook was successfully deleted. No response body is returned.

Error Codes

CodeWhen it happens
401Token missing, expired, or invalid
403Insufficient permissions
404Webhook with the specified id does not exist
500Internal server error

Common Mistakes

  • Attempting to delete a webhook using an id that belongs to a different partner — the request will return 404.
  • Deleting a webhook that is still actively receiving production traffic; ensure downstream systems are updated before deletion.
  • Expecting a response body — a 200 response on this endpoint returns no content.

Related Endpoints

  • POST /api/Partners/webhooks — Create a new webhook for the partner
  • GET /api/Partners/webhooks — Retrieve the list of all webhooks configured for the partner
  • PUT /api/Partners/webhooks/{id} — Update an existing webhook configuration

Example

curl -X DELETE https://api.banking.netevia.dev/api/Partners/webhooks/123 \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"
Path Params
int32
required
Response
200

Success

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here!