Skip to main content

Add Member to KYC Group

Adds one address to a KYC group.

Asynchronous: the member is recorded at once and shows up in List KYC Group Members, and the on-chain call is queued, signed by the KYC token's owner wallet. It is recorded as a node transaction of type 39 (AddMemberToKycGroup) on the platform owner node, with internal_id set to the group's id; see Asynchronous writes.

Only the platform owner (root) node may call it.

Required permission: kyc:group:member:create

Request​

POST /v2/admin/kycs/{kyc_token_id}/groups/{group_id}/members

Parameters​

NameTypeInDescription
kyc_token_idstringpathRequired. The KYC token's id, from List KYC Tokens
group_idstringpathRequired. The group's id (24-character hex), not its numeric group_id

Headers​

NameDescription
AuthorizationRequired. Bearer <access_token>
Content-TypeRequired. application/json

Body​

FieldTypeRequiredDescription
user_addressstringYesThe wallet address to add. Stored exactly as sent; its format is not checked

Example​

curl --request POST \
--url '{{baseUrl}}/v2/admin/kycs/68c4a1f2b9e3d70012a5c3e8/groups/68d2e7a9c1b4f30045e1a9b2/members' \
--header 'Authorization: Bearer <access_token>' \
--header 'Content-Type: application/json' \
--data '{
"user_address": "0x1234567890123456789012345678901234567890"
}'

Response​

Status 201.

{
"requires_approval": false,
"completed": true
}

Response Fields​

FieldTypeDescription
requires_approvalbooleanAlways false: KYC writes have no approval step
completedbooleantrue once the request is accepted and the on-chain call is queued. It does not mean the chain has confirmed it

Errors​

StatusCodeDescription
40010015Validation failed — see details
40310005 (domain 2)Your node is not the platform owner (root) node
40020001001KYC group not found, or it lives on another KYC token than the path names
40010015The KYC token cannot be resolved (kyc token not found or not deployed)
50010000The address is already a member of this group

See Errors for the error format and common codes.