Mint, redeem, and bridge all post to the same endpoint, POST /v2/stablecoins/conversion. The sourceAssetType and destinationAssetType you pass determine which operation runs. This page covers how the three differ and the fields they share; each operation has its own page with the full payload.
The three operations
Shared request fields
Every conversion takes the same core fields, whatever the direction:
Generate a fresh idempotencyKey (for example, a v4 UUID) for each conversion and reuse it only when retrying that same conversion. This makes an interrupted call safe to repeat without minting or burning twice.
What you get back
A successful request returns authorizationOperationId, and the conversion enters INITIATED status pending endorsement approval. Follow it to completion with the history and transactions endpoints—see Track conversion status.
Which to use
- Mint when you’re issuing stablecoins from USD you hold at Anchorage Digital.
- Redeem when you’re converting stablecoins back into spendable USD.
- Bridge when you need the same stablecoin on a different chain without leaving custody.
