whitelist
Prepares the unsigned transaction that whitelists or blacklists investor wallets for a token.
POST /prepare-transactions with method=whitelist.
Next step
Preparing does not touch the chain. The response gives youtxId and an array of unsigned transactions — you still have to sign and submit them.
Sign every returned transaction
signerAddress, or investorAddress for newInvest and claimTokens. It must be whitelisted by Brickken, and it needs native gas on the target chain.Submit the signed payloads
POST them to /send-transactions as { txId, signedTransactions } and Brickken broadcasts for you.If you would rather broadcast yourself, prepare with executionMode: "client-broadcast" and confirm afterwards with { txId, txHash } instead.Poll until it confirms
GET /get-transaction-status with the txId. A pending status means it is broadcast but not yet mined — do not resubmit.Authorizations
Body
Required. Operation to prepare. Must be whitelist for this endpoint.
whitelist "whitelist"
Required. Blockchain network identifier. Hex format is recommended, for example Sepolia aa36a7.
"aa36a7"
Required. Tokenizer wallet that signs the whitelist transaction.
"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"
Required. Symbol of the token whose whitelist is updated.
"EXMPL"
Required. Users to whitelist or blacklist.
1Optional. Default profile data used when creating missing investor users.
Response
Successful response
Array of unsigned transaction objects ready for signing
Unique identifier for this transaction batch (required for /send-transactions). This is NOT a blockchain transaction hash.
"0x46adea7bdf49c576a760102e0d6bc9ecd650b3998588cd3d7f576a7973426aad"
Metadata about the operation