Tokenize an Asset
Map a real-world tokenization use case to the right SDP template, authorities, and API flow.
Use this guide when you want to issue a stablecoin, tokenized security, loyalty token, or another asset through Solana Developer Platform. It is the fastest public path from business case to the actual SDP API flow.
Start with the right token model
| Asset model | Recommended template | Typical controls |
|---|---|---|
| Fiat-backed stablecoin | stablecoin | Mint authority, freeze authority, pausable, permanent delegate |
| Tokenized security | tokenized-security | Allowlists, freeze authority, pausable, permanent delegate |
| Loyalty, rewards, or non-standard utility token | custom | Manually selected metadata and extension set |
| Non-standard asset model | custom | Manually selected metadata and extension set |
Default to SDP-controlled custody wallets for your main authorities when you expect SDP execute flows to work without external signing.
The implementation sequence
- Set Up Your Organization
- Set Up Wallets
- Manage API Keys
- Create a Token
- Deploy a Token
- Mint and Burn Tokens
- Transfer Tokens
- Manage Allowlists and Freeze and Compliance when regulation or policy requires them
API-first flow
If you are integrating through the API, these are the core public issuance and movement endpoints:
GET /v1/walletsPOST /v1/api-keysGET /v1/issuance/templatesPOST /v1/issuance/tokensPOST /v1/issuance/tokens/{tokenId}/deployPOST /v1/issuance/tokens/{tokenId}/mintPOST /v1/issuance/tokens/{tokenId}/authorityPOST /v1/issuance/tokens/{tokenId}/freezePOST /v1/issuance/tokens/{tokenId}/pausePOST /v1/payments/transfersPOST /v1/compliance/address-screeningsfor regulated screening workflows
See the full public endpoint map in the Issuance API reference, Payments API reference, Wallets API reference, API Keys API reference, Projects API reference, and Compliance API reference.
Operational constraints
- A token must be created before deployment, and deployed before minting or transfer operations.
- Token actions that target an account may accept either a wallet address or a token account address depending on the endpoint. Freeze and unfreeze flows accept a holder wallet address and derive the associated token account when possible.
- If the relevant authority is external to SDP custody, prefer prepare flows or rotate the authority to a controlled wallet first.
- If the token is paused, minting and transfer-related operations should be treated as unavailable until it is unpaused.
For coding agents
If you are driving SDP through an agent workflow, start from the public AI docs guide:
That page links the machine-readable SDP discovery files and keeps AI-facing guidance grounded in the supported public docs and API surface rather than internal handlers.