Add Multiple to Blacklist
Adds up to 100 addresses to a token's blacklist in one on-chain call. The request succeeds or fails as a whole: if any address is already on the list, or appears twice in the request, nothing is added.
Asynchronous: the rules are recorded at once and show up in Get Token Blacklist, and the on-chain call is queued. It is recorded as a node transaction of type 46 (AddMembersToBlacklist) on the platform owner node, with internal_id set to the token's id; see Asynchronous writes.
Pass the token's own setup_id (from Get Token): the call runs on the KYC token that setup is wired to and is signed by that KYC token's owner wallet. Your node must be the token's node or one of its ancestors.
Required permission: kyc:blacklist:create
Request
POST /v2/admin/tokens/{token_id}/kyc/blacklist/bulk
Parameters
| Name | Type | In | Description |
|---|---|---|---|
token_id | string | path | Required. The asset token's id |
Headers
| Name | Description |
|---|---|
Authorization | Required. Bearer <access_token> |
Content-Type | Required. application/json |
Body
| Field | Type | Required | Description |
|---|---|---|---|
setup_id | string | Yes | The setup whose KYC token the rules are written to: the token's own setup_id |
user_addresses | array of string | Yes | 1–100 wallet addresses. Stored exactly as sent; their format is not checked |
Example
curl --request POST \
--url '{{baseUrl}}/v2/admin/tokens/68ae06cfcccf4e8fc19362d1/kyc/blacklist/bulk' \
--header 'Authorization: Bearer <access_token>' \
--header 'Content-Type: application/json' \
--data '{
"setup_id": "68b1c2d3e4f5a6b7c8d9e0f1",
"user_addresses": [
"0x1234567890123456789012345678901234567890",
"0x0987654321098765432109876543210987654321"
]
}'
Response
Status 201.
{
"requires_approval": false,
"completed": true
}
Response Fields
| Field | Type | Description |
|---|---|---|
requires_approval | boolean | Always false: KYC writes have no approval step |
completed | boolean | true once the request is accepted and the on-chain call is queued. It does not mean the chain has confirmed it |
Errors
| Status | Code | Description |
|---|---|---|
| 400 | 10015 | Validation failed — see details. Also an empty list or more than 100 addresses |
| 400 | 10016 | token_id is not a valid id |
| 400 | 10001 (domain 5) | Token not found |
| 403 | 10005 (domain 2) | The token belongs to a node outside your node's subtree |
| 400 | 10015 | setup_id names no setup, or the setup has no network or no KYC token (message says which) |
| 500 | 10000 | An address is already on this list or appears twice in the request; nothing was added |
See Errors for the error format and common codes.