Launch a token

POST /launch is the create-token flow. It needs the launch scope. The token becomes a project in your account, with its tasks, exactly like a launch from the app.

Body#

{
  "launchpad": "pump",
  "name": "Vortex Cat",
  "symbol": "VCAT",
  "description": "gm",
  "twitter": "https://x.com/…",
  "imageUrl": "https://example.com/cat.png",
  "creatorWalletId": "812",
  "devBuySol": 0.5,
  "buys": [
    { "walletId": "813", "amountSol": 0.3 },
    { "privateKey": "…", "amountSol": 0.2 }
  ],
  "dryRun": false
}

Private keys become wallets in your account, the same as importing them on the Wallets page.

Launch tasks#

tasks is step 3 of the create wizard, in JSON: the tasks that should fire the moment the token exists, written on the launch itself. You don't create them first on the Tasks API; the launch creates them for its mint. Each task is:

{
  "launchpad": "pump",
  "name": "Vortex Cat",
  "symbol": "VCAT",
  "imageUrl": "https://example.com/cat.png",
  "creatorWalletId": "812",
  "devBuySol": 0.5,
  "buys": [{ "walletId": "813", "amountSol": 0.3 }],
  "tasks": [
    { "type": "volume", "walletIds": ["814", "815"], "config": { "minBuySol": 0.02, "maxBuySol": 0.05, "minDelayMs": 2000, "maxDelayMs": 8000 } },
    { "type": "antisniper", "walletIds": ["813", "814", "815"], "config": { "thresholdPercent": 5, "action": "sell_all" } },
    { "type": "dca", "walletIds": ["816"], "autostart": false, "label": "later", "config": { "side": "buy", "everyMs": 60000, "sizeUnit": "native", "sizeValue": 0.01, "maxFires": 10 } }
  ],
  "dryRun": false
}

• buys is the short form of one bundle task; you can send both.
• Settings are checked at the door with the engine's own rules. A wrong value refuses the whole launch as 400 validation_failed, naming tasks[i].config, before anything is pinned or minted.
• The tasks follow the launch: a sent launch creates them on the new project and starts the autostart ones; the response lists them in tasks with their taskId, started, or an error. Engines with no simulation of their own (bundle, volume, antisniper, the order tasks) can't ride a simulated launch, so simulate with the other tasks and send with all of them.
• A task's dryRun setting is ignored: the launch's dryRun decides for every task on it.

POST /launch/affordability takes the same tasks shape, so you can price the plan before you send.

Which quotes can I launch with?#

Two read calls answer it, from the same rules and lists the create modal uses:

GET /launchpads:

{
  "launchpads": [
    {
      "launchpad": "pump",
      "name": "Pump.fun",
      "chain": "solana",
      "quoteTokens": ["sol", "usdc", "stock"],
      "quotes": [
        { "quoteToken": "sol", "symbol": "SOL", "decimals": 9, "address": null, "pairToken": "none", "devBuyField": "devBuySol" },
        { "quoteToken": "usdc", "symbol": "USDC", "decimals": 6, "address": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v", "pairToken": "none", "devBuyField": "devBuyQuote" },
        { "quoteToken": "stock", "symbol": "STOCK", "decimals": null, "address": null, "pairToken": "required", "devBuyField": "devBuySol" }
      ],
      "liveQuoteList": true
    }
  ]
}

GET /launchpads/stonkfun/quotes — the tokenized stocks StonkFun launches in today. Copy quoteToken and pairToken straight into the launch body:

{
  "launchpad": "stonkfun",
  "chain": "solana",
  "quotes": [
    {
      "quoteToken": "stock",
      "pairToken": "Xsc9qvGR1efVDFGLrVsmkzv3qi45LTBjeUKSPmx9qEh",
      "symbol": "TSLAx",
      "name": "Tesla xStock",
      "decimals": 8,
      "address": "Xsc9qvGR1efVDFGLrVsmkzv3qi45LTBjeUKSPmx9qEh",
      "kind": "stock",
      "devBuyField": "devBuySol",
      "approved": true,
      "category": "Technology",
      "logoUrl": "https://…"
    }
  ]
}

• pump lists SOL, USDC and the stocks pump.fun's on-chain whitelist allows. stonkfun lists only stocks. raydium_launchlab, bonk and bonkers list SOL and USD1. meteora_dbc lists SOL. pons lists ETH plus the approved pair tokens (USDG, tokenized stocks) launches on Robinhood Chain have used; any other approved contract can still be sent as pairToken.
• devBuyField tells you where the creator's first buy goes: devBuySol is spent in SOL and swapped into the quote when needed, devBuyQuote is spent in the quote the creator holds, devBuyEth on pons.
• A stock quote is a live list: an entry can disappear when the venue stops listing it. The launch checks the pair again when it runs. When the venue's list is unreachable the answer is 503 with code: "service_unavailable"; retry.
• An unknown launchpad is 404 with code: "not_found".

Response#

A sent launch returns the mint, the on-chain signature, the hosted metadata uri and imageUri, the new projectId, and the tasks it created:

{
  "mint": "J11LopwNEF3wkMQGskM3jVmEMmncqdkadQ1b6PuXpump",
  "creator": "6729VKWPgq1qTaxkv2n1SVPzDc1A2tajiNTvS3uUCE88",
  "launchpad": "pump",
  "quoteToken": "sol",
  "pool": null,
  "dryRun": false,
  "signature": "3BNESKPXnqoAfSpgSrjCsz9CnWNCTRiXzHQYuR3jLgqx8KQSJgvVLrdu7WRvjZDpFYjGDtZKnhQviRj7MngM5L98",
  "confirmed": true,
  "err": null,
  "devBuyTokens": null,
  "projectId": "1021",
  "uri": "https://api.vortexdeployer.com/metadata/….json",
  "imageUri": "https://api.vortexdeployer.com/image/….png",
  "tasks": []
}

A simulation (dryRun: true) returns the same shape with confirmed: false, signature: null, and a simulation object instead of projectId/imageUri:

{
  "mint": "J11LopwN…pump",
  "creator": "6729…CE88",
  "launchpad": "pump",
  "quoteToken": "sol",
  "pool": null,
  "dryRun": true,
  "signature": null,
  "confirmed": false,
  "err": null,
  "devBuyTokens": null,
  "simulation": { "err": null, "unitsConsumed": 100811, "logsTail": ["…"] },
  "uri": "https://api.vortexdeployer.com/metadata/….json"
}

With launches over 1, a batch report lists every mint and where the run stopped.

Before you launch: the helpers#

The create modal's checks are routes too. All are read except the upload, which is launch.

Supply plans#

A supply plan is a saved bundle layout in % of supply per wallet slot. GET /supply-plans lists yours (paged), POST /supply-plans saves one (trade), DELETE /supply-plans/:id removes it.

{
  "name": "12 wallets, 18%",
  "slots": [ { "targetPercent": 1.5, "walletId": "812" }, { "targetPercent": 1.5, "role": "trading" } ],
  "maxTotalPercent": 18,
  "maxWalletPercent": 2
}

A slot pins a walletId or names the role a wallet must carry; an open slot takes the next wallet you select when the plan is mounted. POST /supply-plans/:id/mount resolves the plan against wallets and a curve: { "walletIds": [ … ], "launchpad": "pump", "quoteToken": "sol" } for a fresh curve, or mint for a token already trading, and answers per row the wallet, its slot, the coin it must spend and any shortfall.

Refusals#

A restricted key (caps, wallet list or sandbox) can only simulate launches. See API overview & keys.

See also#

• Create a project in the app
• Create, edit and delete a project: a draft project before the launch, wallets in it, close-out after
• Tasks API