Mint a Tokenized Asset

post

https://broker-api.sandbox.alpaca.markets/v1/accounts/{account_id}/tokenization/mint

This endpoint is used by an Authorized Participant to request the minting of a tokenized asset. Alpaca will initiate a journal of the underlying asset from the Authorized Participant's account to the issuer's account.

Idempotency: When the Idempotency-Key header is supplied, this endpoint is
idempotent. Multiple requests with the same key and identical request body will
create only one mint request. A subsequent request returns the previously created
request with the same response (no duplicate is created). If the same key is used
with a different request body, the API returns 422 Unprocessable Entity.

Recommended for production: Always supply Idempotency-Key when requesting a
mint. This allows safe retries on timeouts, network errors, or 5xx responses
without risking duplicate requests. Use a client-generated unique value (e.g. UUID).

Path Params

account_id

uuid

required

Account identifier.

Body Params

issuer

string

enum

required

The tokenized asset's issuer

Allowed:

network

string

enum

required

The token's blockchain network

qty

string

required

The underlying quantity to convert into the tokenized asset. It can be fractional.

underlying_symbol

string

required

The underlying asset symbol

wallet_address

string

required

The wallet address to receive the tokenized asset

Headers

Idempotency-Key

string

length ≤ 128

Unique key for idempotent create. When supplied, duplicate requests (same key
and body) return the original mint request instead of creating a new one. Use a
client-generated value (e.g. UUID) per logical request. Strongly recommended
for production to prevent duplicate requests on retries.

Responses

Language

Credentials

Basic

base64

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successfully requested minting of a tokenized asset.

400Bad request (e.g. malformed input, insufficient position, or account not authorized to mint). Also returned when the Idempotency-Key header is malformed, or when replaying a request that was originally rejected.

401Authentication credentials are missing or invalid.

403Caller is not authorized to perform this operation.

422One or more request parameters are missing or invalid, or the same Idempotency-Key was reused with a different request body.