Delete a notification endpoint
Notification
Delete a notification endpoint
POST
Delete a notification endpoint
Deletes one registered notification endpoint, identified by the
apiNotificationId returned by List notification endpoints. One endpoint per call. The response carries no payload — read meta.status to confirm.
You can only delete endpoints your account registered through this API. An apiNotificationId that does not exist, or belongs to another account, fails with HTTP 200, meta.status 400, meta.errorCode VALIDATION_FAILED, and:
Idempotency
Thex-returnhelper-idempotency-key header is optional. A call without it runs normally, with no protection against duplicates. See Idempotency.
Related
Authorizations
Your API key
Your API token — keep this private
Body
application/json
Identifier of the notification endpoint to delete, as returned by /api/Notification/GetAll.
Example:
1234
Response
Success — returns the standard response envelope with no additional payload fields. Inspect meta.status to confirm the deletion succeeded.
Universal response envelope. Successful responses include the business payload as additional top-level fields alongside correlationId and meta. Failed responses (auth errors, validation errors) only populate correlationId and meta, with meta.errorCode and meta.error describing the failure.