Overview
Creates an unsigned transaction for launching a new SPL token on Solana with custom metadata, optional vanity address ending, no fees, automatic inflation and claimability.Request Parameters
The display name of the token (e.g., “Solana Token”)
The token symbol/ticker (e.g., “SOL”, “USDC”)
Base58 encoded public key of the account that will pay transaction fees and own the token
Optional description of the token for metadata
URL to the token’s image/logo for metadata
Website URL associated with the token
Twitter URL or handle for the token project
Optional vanity ending for the token address (max 3 characters, no 0, O, I, l)
Quote token for the bonding curve pool. Options: “SOL” (default) or “ZC” (native launchpad token). If not specified, defaults to “SOL”
Response
Indicates if the operation was successful
Base58 encoded unsigned transaction that needs to be signed by the payer
The public key of the token mint address
IPFS URL where the token metadata is stored
Instructions for the next step in the process
Success Response
Error Responses
400 - Missing Required Fields
400 - Missing Required Fields
400 - Invalid CA Ending
400 - Invalid CA Ending
500 - Server Error
500 - Server Error
Rate Limiting
This endpoint is subject to rate limiting:- 8 requests per IP per 2-minute window
- Returns HTTP 429 when limit exceeded
Next Steps
After receiving the unsigned transaction:- Deserialize the transaction using
@solana/web3.js
- Sign the transaction with your wallet
- Submit the signed transaction to
/confirm-launch
The
baseMint
and internal keypair are stored temporarily. You must call /confirm-launch
within a reasonable time frame or the launch will need to be restarted.Security Notes
- The API generates the token keypair internally and does not expose the private key
- Users only sign for transaction fees and account creation
- Protocol maintains mint authority for the claims system
- All metadata is uploaded to IPFS for permanent storage