Classifications

Delete a classification

DELETE/classifications/{id}
classifications:writedelete_classificationDestructiveIdempotent

Deletes the classification and returns 204. Every investor loses it, deals stop using it for visibility, and onboarding flows stop checking for it. It can't be undone and has no dry run. Callers without the manage-classifications permission get 403 missing_permission. Emits classification.deleted; no emails or notifications are sent.

Path parameters

  • idintegerRequired#

    The classification's id. Classifications are keyed by integer ids, not UUIDs: a whole number from 1 to 2147483647.

Responses

204

The classification was deleted.

401

Authentication failed. error.code is one of invalid_token, expired, revoked.

Error
403

Authorization failed. error.code is missing_permission when the caller lacks the manage-classifications permission, with its name in details, or one of missing_scope, scope_disabled, org_disabled, ip_blocked, user_disabled.

Error
404

Resource not found (error.code = not_found).

Error
422

The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per problem, or a code documented on the operation.

Error
429

Rate limit exceeded (error.code = rate_limited).

Error

Examples

curl -X DELETE https://your-org-domain/kong/core/api/v2/classifications/{id}\
  -H "Authorization: Bearer $HELM_API_KEY"\
  -H "Content-Type: application/json"