Update a KYC level
/v1/kyc/levels/{level_key}Requires an API client bearer token.
Replaces a level's display name and/or definition (at least one). With `expect_updated_at` the write lands only if the level is still the revision the caller read (409 `level_conflict` otherwise). A definition that cannot be used is a 400 `invalid_level` carrying `problems[]`. A published policy keeps its own frozen snapshot, so editing a level never changes one. Requires Idempotency-Key and the programme_admin role.
Parameters
Path parameters
| Name | Required | Description |
|---|---|---|
| level_key | required |
Header parameters
| Name | Required | Description |
|---|---|---|
| Idempotency-Key | required | Client-chosen. An identical retry with the same key returns the stored response; reusing the key with a different payload returns 409. |
Request body
+ show properties− hide properties
+ show properties− hide properties
+ show properties− hide properties
One of
typed
+ show properties− hide properties
block
untyped
+ show properties− hide properties
Example
curl -X PUT https://api.rigid.fi/v1/kyc/levels/{level_key} \
-H "Authorization: Bearer $RIGID_API_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"programme_id": "uuid"
}'Responses
200The updated level.
+ show properties− hide properties
+ show properties− hide properties
+ show properties− hide properties
One of
typed
+ show properties− hide properties
block
untyped
+ show properties− hide properties
400Validation error
401Authentication required
403Forbidden
404No level with this key for this programme
409The level changed since it was read (code `level_conflict`), or the Idempotency-Key was reused with a different payload
429Too many policy writes from this caller — see Retry-After
500Internal server error