Whitelist a Crypto Account - BoomFi

Register a wallet you control as a payout destination. See Overview for why registration is the security-sensitive step.

Register

curl -X POST "https://mapi.boomfi.xyz/v1/accounts/external-account" \
  -H "X-API-KEY: sk_test_xxx" \
  -H "X-Step-Up-Token: <step-up-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "Digital",
    "reference": "treasury-base",
    "name": "Treasury (Base)",
    "currencies": ["USDC"],
    "chain_id": 8453,
    "address": "0xRecipientWallet…"
  }'

X-Step-Up-Token is required when you authenticate with a Bearer session; it is ignored for API-key auth. The account is enabled immediately — registering it is the approval.

Field	Type	Required	Description
`type`	string	yes	`Digital`
`reference`	string	yes	Your own reference for this account. Used to address it on a payout
`name`	string	yes	Display name
`currencies`	array	yes	One or more currency symbols this address can receive on `chain_id`
`chain_id`	number	yes	Destination chain id
`address`	string	yes	Destination wallet address, validated for the chain’s address format

A second registration with the same reference on the same chain_id returns 409.

List

curl "https://mapi.boomfi.xyz/v1/accounts/external-account?type=Digital" \
  -H "X-API-KEY: sk_test_xxx"

Returns every registered external account; filter with ?type=Digital to see only crypto destinations. Response fields for a digital account: id, reference, name, currencies, chain_id, address, enabled, created_at.

Remove

curl -X DELETE "https://mapi.boomfi.xyz/v1/accounts/external-account/123" \
  -H "X-API-KEY: sk_test_xxx" \
  -H "X-Step-Up-Token: <step-up-token>"

Payouts already in flight are unaffected; new payouts can no longer name this account.

Next steps

Once registered and enabled, pay out to this account by its id or reference.