---
title: Tokenize an Asset
description: 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

1. [Set Up Your Organization](/docs/guides/setup-organization)
2. [Set Up Wallets](/docs/guides/setup-wallets)
3. [Manage API Keys](/docs/guides/manage-api-keys)
4. [Create a Token](/docs/guides/create-a-token)
5. [Deploy a Token](/docs/guides/deploy-a-token)
6. [Mint and Burn Tokens](/docs/guides/mint-and-burn)
7. [Basic payment](/docs/payments/send-basic-payment)
8. [Manage Allowlists](/docs/guides/manage-allowlists) and [Freeze and Compliance](/docs/guides/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/wallets`
- `POST /v1/api-keys`
- `GET /v1/issuance/templates`
- `POST /v1/issuance/tokens`
- `POST /v1/issuance/tokens/{tokenId}/deploy`
- `POST /v1/issuance/tokens/{tokenId}/mint`
- `POST /v1/issuance/tokens/{tokenId}/authority`
- `POST /v1/issuance/tokens/{tokenId}/freeze`
- `POST /v1/issuance/tokens/{tokenId}/pause`
- `POST /v1/payments/transfers`
- `POST /v1/compliance/address-screenings` for regulated screening workflows

See the full public endpoint map in the [Issuance API reference](/docs/reference/api/issuance), [Payments API reference](/docs/reference/api/payments), [Wallets API reference](/docs/reference/api/wallets), [API Keys API reference](/docs/reference/api/api-keys), [Projects API reference](/docs/reference/api/projects), and [Compliance API reference](/docs/reference/api/compliance).

## 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:

- [AI Consumption](/docs/reference/ai-consumption)

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.
