Skip to main content
Before making a conversion, identify the source and destination wallets and confirm the exact assetType strings you’ll use. Then make sure your API key has the right permission and authentication.

​
Identify wallets and asset types

  • GET /v2/vaults/{vaultId} — Retrieve walletId values and balances for the vault holding the source funds.
  • GET /v2/asset-types — Look up exact assetType strings, including chain-specific variants like USDX_BSC_T.
Confirm the exact chain-specific assetType for both legs before you bridge. The source and destination are the same stablecoin on different chains, so a wrong variant routes funds to the wrong network.

​
Permission

The API key must have the Convert Stablecoins vault permission. Configure it via Permission groups.

​
Authentication

Stablecoin conversion and history endpoints require only the Api-Access-Key header. No Api-Signature or Api-Timestamp headers are needed.
This differs from most money-movement endpoints, which require an Ed25519 request signature. See Request signing for the general signing model.