POST /api/tokens/deploy. The example request and field tables below cover every v5 field. For how v5 tokens work, see Token Deployments. For the full endpoint reference, see Deployment.
How it works
- Send a
POSTrequest tohttps://www.clanker.world/api/tokens/deploywith your partner API key in thex-api-keyheader. - Add a
taxobject to set the tax. Without one, the token launches with a 1% buy and sell tax. - The response gives the expected token address. The deployment is queued and lands on chain shortly after.
dryRun: true to check a request without deploying.
Each API key can launch 20 tokens per day and 1 per minute unless Clanker set other limits for it. Over a limit, the route returns 429 with Retry-After.
Example request
This request launches a USDC-paired token with a 5% buy and sell tax. It sends 20% of the creator share to holder dividends and 10% to burns, and splits the rest between two reward recipients.dryRun: true, nothing is deployed. The response gives "message": "Dryrun successful" and the nativeLaunchFee in wei.
Request fields
Launch and token
Tax
dividends, burn and the integrator share together must not exceed 100. The rest of the tax after the Clanker fee goes to the reward recipients.
Pool and rewards
The route does not accept v4 fields (
fees, other pool settings, vault, airdrop, poolExtension or devBuy). A request that includes them returns a 400 error that lists them.
Launch policy
GET /api/metadata/factories lists each Clanker factory. The v5 factory’s taxPolicy field gives the current launch policy: tax bounds, Clanker fee, sniper fee and dividend minimum. When taxPolicy.launchCreationEnabled is false, a deploy returns a 400 error. See Launch policy in the v5 contracts for each field.
Related
- Rewards: see Creator Rewards & Fees.
- Dividends and burns: see Holder Dividends and Token Burns.
- Metadata, reward recipients, admins and verification: see Managing a Token.