Create a classification
/classificationsCreates a classification in the organisation and returns it with a Location. A label another classification already has, ignoring case, returns 422. Callers without the manage-classifications permission get 403 missing_permission; holders of the assign-only permission can't create. dry_run shows the result without saving it. Emits classification.created and sends no email. DELETE /classifications/{id} undoes it.
Query parameters
Validate and run the call without committing it, returning what the real call would return with
meta.dry_runset.
Headers
Makes a retry safe. Send a new UUID for each new request and reuse it only to retry that request; the first response is replayed for 24 hours.
Request body
application/json, required · ClassificationCreate
The name investors and staff see, such as Sophisticated Investor. Letters, digits, spaces and - . , & only. Another classification can't have the same label, ignoring case.
{
"label": "Sophisticated Investor"
}Responses
{
"data": {
"id": 1,
"label": "string",
"member_count": 1,
"created_at": "2026-06-12T10:00:00+00:00",
"updated_at": "2026-06-12T10:00:00+00:00"
}
}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.
The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per
problem, or a code documented on the operation.
Examples
curl -X POST https://your-org-domain/kong/core/api/v2/classifications\
-H "Authorization: Bearer $HELM_API_KEY"\
-H "Content-Type: application/json"\
-d '{
"label": "Sophisticated Investor"
}'