Assign an investor's key contact
/investors/{userId}/key-contactAssigns the user's key contact / advisor — an internal user who owns the
relationship with this user. The advisor is supplied under keyContactId
(or userId) and must be a user in the same organisation.
Deprecated: withdrawn on 2027-06-30. POST /investors/{id}/actions/set-key-contact replaces it; every answer carries a Link header with rel="successor-version". This route keeps its old body and answer.
Path parameters
The user's public guid.
Request body
application/json, required
{
"keyContactId": "9f8e7d6c-5b4a-4039-8271-6e5d4c3b2a19"
}Responses
OK
{
"data": {
"user_id": "6f1c2e8a-1b2c-4d5e-8f90-1a2b3c4d5e6f",
"key_contact_id": "9f8e7d6c-5b4a-4039-8271-6e5d4c3b2a19"
}
}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 PUT https://your-org-domain/kong/core/api/v2/investors/{userId}/key-contact\
-H "Authorization: Bearer $HELM_API_KEY"\
-H "Content-Type: application/json"\
-d '{
"keyContactId": "9f8e7d6c-5b4a-4039-8271-6e5d4c3b2a19"
}'