Verify an onboarding implementation
/onboarding/implementations/{implementationId}/verificationSensitive. Records a verification row against the implementation with the supplied verified text, in any state and every time it is called. The verifier is the token's own user. Deprecated: withdrawn on 2027-06-30. POST /onboarding-sessions/{id}/actions/verify replaces it; the Link header names it.
Path parameters
The compliance implementation's public uuid.
Request body
application/json, required
The verification status to record.
{
"verified": "Approved"
}Responses
{
"data": {
"id": "1f0c9e8d-7b6a-4039-8271-6e5d4c3b2a19",
"compliance_id": "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d",
"user_id": "a1b2c3d4-e5f6-4071-8293-a4b5c6d7e8f9",
"flow_test": false,
"expired": false,
"start_date": "2026-06-15T10:30:00+00:00",
"end_date": "2026-06-15T10:45:00+00:00",
"created_at": "2026-06-15T10:30:00+00:00",
"updated_at": "2026-06-15T10:45:00+00:00"
}
}Authorization failed. error.code is one of org_disabled,
ip_blocked, missing_scope, scope_disabled, user_disabled.
Request validation failed (HTTP 422). The body is either the Laravel
validation envelope (message + field-keyed errors) or the API error
envelope for domain rejections (e.g. form_type_not_supported,
folder_locked, parent_not_found, folder_not_empty).
Examples
curl -X POST https://your-org-domain/kong/core/api/v2/onboarding/implementations/{implementationId}/verification\
-H "Authorization: Bearer $HELM_API_KEY"\
-H "Content-Type: application/json"\
-d '{
"verified": "Approved"
}'