Update the allowlist

Add addresses to a token's allowlist or remove them. EVM tokens take one change per request. Liquid tokens take up to 100 additions and 100 removals. A blocklist token returns 409 WRONG_COMPLIANCE_MODE. Building first is optional: omit transaction to build and submit in one call, or build with POST .../compliance/allowlist/build, review the result, and send it unchanged as transaction.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
length ≥ 1

Token ID.

Body Params
boolean
Defaults to false

Set to true to simulate the transaction, as sent by the signing vault, before anything is signed. A predicted revert returns 422 SIMULATION_REVERTED, for example when the recipient is not on the allowlist, the vault does not hold the role, or the token is paused. On io.chain this is the only revert check before signing. On public chains a transaction that would revert is refused even without this flag. If the simulation cannot run, the call returns 503 SIMULATION_UNAVAILABLE and nothing is built or submitted. Defaults to false.

add
array of objects
length ≤ 100
Defaults to []
add
remove
array of strings
length ≤ 100
Defaults to []
remove
transaction
object

The unsigned transaction from the matching /build endpoint, sent unchanged. Omit it to build and submit in one call.

Headers
string
length between 1 and 255

Key that makes this call safe to retry. Repeating the key with the same body returns the original response without running the operation again. Reusing the key with a different body is refused. Keys are scoped to you and this operation, so the same key on another operation does not collide. Keys expire some time after the original call completes. An empty or whitespace-only value is rejected. Maximum length: 255 characters.

Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json