Skip to content
API Reference

Search is only available in production builds. Try building and previewing the site to test it out locally.

Launch trading

Quote, buy, sell, transfer, burn and lock the token of a live launch from its wallets.

Once a launch is live, these calls trade its token from the launch wallets: buy back with several wallets at once, sell the dev or sub-wallet supply, or sell everything with a nuke. Amounts are integer strings in base units of the token or the quote.

Trades are signed with the wallets' stored keys and sent on-chain; the response reports what landed.

Quote a trade

Bearer JWT
POST /launch/quote/{launch_id}

Simulates buys or sells of the launch token for one or more amounts.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Safe to retry A pure read sent as POST: it prices the amounts and sends nothing.

Returns one leg per amount, in the same order. The app refreshes it every 5 seconds while a trade form is open.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • direction enum Required
    Buy or sell the token.
    Possible values buysell
  • mode enum Required
    exact_in quotes what an input amount returns; exact_out what an output amount costs.
    Possible values exact_inexact_out
  • amounts array<string> Required
    Amounts to quote, in base units, as integer strings.

Returns 200 OK · application/json

Returns a JSON array of legs.

  • amount number
    Resulting amount, in base units. EVM launches answer it as an integer string.
  • price_impact number
    Price impact of the trade.
  • mcap_change_bps number | null
    Market cap change, in basis points.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
400 bad_request Solana: a buy was quoted in exact_out mode. Quote buys with exact_in.
400 bad_request EVM: exact_out is not supported in either direction. Quote with exact_in on EVM launches.
400 bad_request EVM: an entry of amounts is not a base-10 integer string. One above 2^128 answers amount too large. Send each amount as an integer string of base units, below 2^128.
500 internal_error Solana: the token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Quote once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request EVM: the token is not deployed yet. Quote once the launch is live, as shown by launch_status in List the license's launches.
422 unprocessable Solana: no sell amount could be priced, and the message is the venue's reason. When only some fail, those legs answer an amount of 0. Read the venue's reason in the message, then quote again.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.quote(launchId, request) src/lib/proxima/endpoints/launch/launch.ts

POST /launch/buyback/info/{launch_id}

Returns the most the selected wallets can spend on a buyback.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Safe to retry A pure read sent as POST: it reads the wallets' balances and sends nothing.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • wallet_sources object Optional
    Wallets to use: either flags include_dev, include_mev and include_holders, or an array of wallet addresses.
    Child attributes 3
    • include_dev boolean Optional
      Include the dev wallet.
    • include_mev boolean Optional
      Include the MEV wallets.
    • include_holders boolean Optional
      Include the holder wallets.

Returns 200 OK · application/json

  • max_buy_amount string
    Largest buyback, in quote base units. Solana launches answer it as a number.
  • eligible_wallet_count integer
    Wallets able to buy.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
500 internal_error Solana: the token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Call it once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request EVM: the token is not deployed yet. Call it once the launch is live, as shown by launch_status in List the license's launches.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.getBuybackMax(launchId, request) src/lib/proxima/endpoints/launch/launch.ts

Buy back the token

Bearer JWT
POST /launch/buyback/{launch_id}

Buys the launch token with several launch wallets at once.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Check before retrying Nothing refuses a repeat, so it buys again. Look for the buy event the call writes in List a launch's activity events before sending it again.

The amount is split across the selected wallets according to selection_mode, dispersion and distribution, then executed one after the other or in parallel. Use Retrieve the buyback maximum to size it.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • amount string Required
    Quote to spend in total, in base units, as an integer string. 0 spends everything available.
  • slippage integer Required
    Slippage tolerance, in basis points.
  • selection_mode enum Optional Default random
    Which wallets buy first.
    Possible values randomlow_tokenshigh_tokens
  • dispersion integer Optional
    How many of the selected wallets buy, from 0 (fewest) to 100 (all).
  • distribution string Optional Default equal
    How the amount is split: equal, weighted, or {"random": {"deviation_pct"}} (deviation defaults to 20).
  • execution object Optional Default stagger
    How the buys are sent.
    Child attributes 2
    • mode enum Optional
      One after the other, or all at once.
      Possible values staggerparallel
    • delay_ms integer Optional Default 1000
      stagger only: delay between buys, in milliseconds.
  • fake_tip_pct number Optional
    Not used to build the trades. EVM refuses a value above 100; Solana ignores it. The app sends 0.
  • wallet_sources object | array<string> Optional
    Wallets to use: either flags include_dev, include_mev and include_holders, or an array of wallet addresses.
    Child attributes 3
    • include_dev boolean Optional
      Include the dev wallet.
    • include_mev boolean Optional
      Include the MEV wallets.
    • include_holders boolean Optional
      Include the holder wallets.
  • terminal enum Optional
    Sent by the SDK, not read by the API.
    Possible values directaxiompadregmgn
  • routing object Optional
    Sent by the SDK, not read by the API.

Returns 200 OK · application/json

  • ok boolean
    true when at least one buy landed. On Solana a buyback where every buy failed still answers 200, with ok: false.
  • message string
    Human-readable outcome.
  • total_wallets integer
    Wallets used.
  • successful integer
    Buys that landed.
  • failed integer
    Buys that failed.
  • total_token_bought number
    Tokens bought, in base units.
  • total_quote_spent number
    Quote spent, in base units.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
400 bad_request EVM: slippage is above 10000 basis points. A stagger delay_ms above 60000 answers Stagger delay cannot exceed 60000ms, and a fake_tip_pct above 100 answers fake_tip_pct must be between 0 and 100. Keep slippage at most 10000, delay_ms at most 60000 and fake_tip_pct at most 100.
500 internal_error Solana: slippage is above 10000 basis points. A stagger delay_ms above 60000 answers Stagger delay cannot exceed 60000ms. Keep slippage at most 10000 and delay_ms at most 60000.
500 internal_error Solana: the token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Buy back once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request EVM: the token is not deployed yet. Buy back once the launch is live, as shown by launch_status in List the license's launches.
422 unprocessable wallet_sources selects no wallet of the launch. Select at least one of the launch's wallets in wallet_sources, as listed by Retrieve a launch.
422 unprocessable None of the selected wallets has quote left to spend. Fund the wallets or select others, then size the buy with Retrieve the buyback maximum.
400 bad_request amount is more than the selected wallets can spend. Size amount with Retrieve the buyback maximum, or send 0 to spend everything available.
422 unprocessable The split gave none of the selected wallets a share of amount. Raise amount or dispersion, then buy again.
422 upstream_failure EVM: every buy reverted. Without a reason from the sender the message ends all buybacks reverted. The buy activity event is still written. Check the reason and the wallets' balances in Retrieve a launch before buying again.
422 unprocessable EVM: every buy was refused for lack of gas. The message names the dev wallet even when the buying wallets are the ones short. Top up the buying wallets' gas, then buy again.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.buyback(launchId, request) src/lib/proxima/endpoints/launch/launch.ts

Sell the dev supply

Bearer JWT
POST /launch/sell-dev-supply/{launch_id}

Sells tokens from the dev wallet.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Check before retrying A repeat sells again. Check the dev wallet's balance in Retrieve a launch and look for the launch.sell_dev_supply event in List a launch's activity events first.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • token_amount string Optional
    Tokens to sell, in base units, as an integer string. 0 sells the whole balance.
  • quote_target string Optional
    Quote to receive, in base units, as an integer string. Use instead of token_amount, not both.
  • fake_tip boolean Optional
    Sent by the app, not read by the API.

Returns 200 OK · application/json

  • ok boolean
    true when the request succeeded.
  • message string
    Human-readable outcome.
  • token_sold number
    Tokens sold, in base units.
  • quote_received number
    Quote received, in base units.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
400 bad_request Solana: token_amount and quote_target were both sent. Send only one of token_amount and quote_target.
400 bad_request EVM: a non-zero quote_target was sent. EVM sales take a token amount only. Pass token_amount instead, sized with Quote a trade if you target a quote amount.
500 internal_error Solana: the token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Sell once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request EVM: the token is not deployed yet. Sell once the launch is live, as shown by launch_status in List the license's launches.
500 internal_error Solana: the launch was imported without its dev wallet's key. Sell the dev supply only on launches whose dev wallet key Proxima holds.
400 bad_request EVM: the dev wallet is watch-only and cannot sign. A launch with no dev wallet answers no dev wallet configured. Sell the dev supply only on launches whose dev wallet key Proxima holds.
422 unprocessable Solana: token_amount is more than the dev wallet holds. Lower token_amount, or send 0 to sell the whole balance.
400 bad_request EVM: token_amount is more than the dev wallet holds. Lower token_amount, or send 0 to sell the whole balance.
422 unprocessable The execution engine cannot carry this sale. On EVM it never carries a sale from wallets its vault holds. Nothing was sent. Do not repeat the call unchanged: the reason names what the execution engine cannot carry.
409 lane_pending Solana: the execution engine sent the sale but has not confirmed it, so it can still land. It also answers this, before sending anything, while the dev wallet has an earlier send unconfirmed. Do not resend: once the hashes in tx_hashes settle, check List a launch's activity events and retry only the part that failed.
422 upstream_failure Solana: the sale was not confirmed as landed. When it was split into several bundles, earlier ones may have landed. Check the dev wallet's balance in Retrieve a launch, then sell again only what is left.
422 upstream_failure EVM: the sale transaction failed, and the message carries the sender's reason. Check the dev wallet's balance in Retrieve a launch before selling again.
422 unprocessable EVM: the dev wallet cannot pay the sale's gas. Top up the dev wallet's gas, then sell again.
409 launch_migrating EVM: the launch is moving from its curve to its pool, so nothing trades it for a few seconds. Wait a few seconds, then sell again.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.sellDevSupply(launchId, request) src/lib/proxima/endpoints/launch/launch.ts

POST /launch/sell-subs-supply/{launch_id}

Sells tokens from the holder and MEV wallets of a launch.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Check before retrying A repeat sells again. Check the wallets' balances in Retrieve a launch and look for the launch.sell_subs_supply event in List a launch's activity events first.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • token_amount string Optional
    Tokens to sell, in base units, as an integer string. 0 sells the whole balance.
  • quote_target string Optional
    Quote to receive, in base units, as an integer string. Use instead of token_amount, not both.
  • fake_tip boolean Optional
    Sent by the app, not read by the API.
  • wallets array<string> Optional
    Wallets to sell from. Omit or send an empty list to sell from every holder and MEV wallet.
  • fake_tip_pct number Optional
    Sent by the app, not read by the API.

Returns 200 OK · application/json

  • ok boolean
    true when the request succeeded.
  • message string
    Human-readable outcome.
  • token_sold number
    Tokens sold, in base units.
  • quote_received number
    Quote received, in base units.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
409 conflict Solana allowlist launch: its run is still trading. Pause the run with Pause an allowlist run, then sell.
400 bad_request Solana: token_amount and quote_target were both sent. Send only one of token_amount and quote_target.
400 bad_request EVM: a non-zero quote_target was sent. EVM sales take a token amount only. Pass token_amount instead, sized with Quote a trade if you target a quote amount.
500 internal_error Solana: the token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Sell once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request EVM: the token is not deployed yet. Sell once the launch is live, as shown by launch_status in List the license's launches.
500 internal_error Solana: a wallet in wallets does not belong to your license. A watch-only wallet answers Wallet is watch-only and cannot sign. List only the launch's holder and MEV wallets in wallets, as shown by Retrieve a launch.
400 bad_request EVM: a wallet in wallets is not one of the launch's. A malformed address answers invalid wallet address: <address>. List only the launch's holder and MEV wallets in wallets, as shown by Retrieve a launch.
400 bad_request EVM: no wallet is left to sell from. Check wallets against the launch's wallets in Retrieve a launch.
500 internal_error Solana: an amount was sent, but the selected wallets hold none of the token. Without an amount the call answers 200 with No tokens to sell. Check the wallets' balances in Retrieve a launch before selling.
422 unprocessable The execution engine cannot carry this sale. On EVM it never carries a sale from wallets its vault holds. Nothing was sent. Do not repeat the call unchanged: the reason names what the execution engine cannot carry.
422 unprocessable Solana: the execution engine's vault signs some of the selected wallets and not others, and one sale cannot mix them. Nothing was sent. Sell the two wallets the message names in separate calls through wallets.
409 lane_pending Solana: the execution engine sent the sale but has not confirmed it, so it can still land. It also answers this, before sending anything, while one of the wallets has an earlier send unconfirmed. Do not resend: once the hashes in tx_hashes settle, check List a launch's activity events and retry only the part that failed.
500 internal_error Solana: not every sale landed. Some may have, and the message does not say which. Check the wallets' balances in Retrieve a launch, then sell again only what is left.
422 upstream_failure EVM: every wallet's sale failed, and the message carries the sender's reason. When only some fail, the call answers 200 with per-wallet counts. Check the wallets' balances in Retrieve a launch before selling again.
422 unprocessable EVM: every sale was refused for lack of gas. The message names the dev wallet even when the selling wallets are the ones short. Top up the selling wallets' gas, then sell again.
409 launch_migrating EVM: every sale failed because the launch is moving from its curve to its pool. Wait a few seconds, then sell again.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.sellSubsSupply(launchId, request) src/lib/proxima/endpoints/launch/launch.ts

Nuke a launch

Bearer JWT
POST /launch/nuke/{launch_id}

Sells every token held by the launch wallets.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Check before retrying A repeat sells only what the wallets still hold, but on EVM nothing refuses it while the first nuke is still selling. Before nuking again, check the balances in Retrieve a launch and the launch.nuke event in List a launch's activity events.

With consolidate, the holders' tokens are first pooled onto one wallet with plain transfers, then sold from it.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • include_dev boolean Optional Default true
    Also sell the dev wallet.
  • consolidate boolean Optional Default false
    Pool the tokens onto one wallet before selling.

Returns 200 OK · application/json

  • ok boolean
    true when the nuke ran. On EVM it stays true when sales failed: read failed.
  • message string
    Human-readable outcome. Solana only.
  • token_sold number
    Tokens sold, in base units.
  • quote_received number
    Quote received, in base units.
  • succeeded integer
    EVM only: wallets that sold.
  • failed integer
    EVM only: wallets that failed to sell.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
400 bad_request Solana: another nuke of this launch is still running. Wait for the running nuke to finish, then check the launch.nuke event in List a launch's activity events.
409 conflict Solana allowlist launch: its run is still trading. Pause the run with Pause an allowlist run, then nuke.
500 internal_error Solana: the token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Nuke only a live launch, as shown by launch_status in List the license's launches.
400 bad_request EVM: the token is not deployed yet. Nuke only a live launch, as shown by launch_status in List the license's launches.
422 upstream_failure Solana: the wallets' balances could not be read. Nothing was sent. Nuke again in a few seconds.
400 bad_request No selected wallet holds the token. EVM answers all wallets have zero token balance, or no wallets to nuke when the launch has no wallets. Nothing is left to sell: confirm with the balances in Retrieve a launch.
400 bad_request EVM: every holder lacks the gas the sale reserves. Top up the holders' gas, or nuke again with consolidate: true.
400 bad_request With consolidate, no holder has enough SOL to pay the pooling and the sale. EVM answers consolidate needs one holder funded enough to pay the sell. Fund one holder, or nuke without consolidate.
400 bad_request EVM, with consolidate: after the pooling transfers, no wallet held tokens to sell. Check the balances in Retrieve a launch, then nuke again without consolidate.
500 internal_error Solana: the launch's platform has no nuke. Sell with Sell the sub-wallet supply and Sell the dev supply instead.
422 unprocessable The execution engine cannot carry this nuke. Refused before the first round, nothing was sent and the message ends Nothing was sent; refused at a later round, the message does not, and earlier rounds may have landed. On EVM it never carries a nuke of wallets its vault holds. Check the balances in Retrieve a launch, and do not repeat the call unchanged.
422 unprocessable Solana: the execution engine's vault signs some of the launch's wallets and not others, and one nuke cannot mix them. Nothing was sent. Sell the wallets the message names separately with Sell the sub-wallet supply.
409 lane_pending Solana: the execution engine sent a sale but has not confirmed it, so it can still land. It also answers this before selling anything, when the bots the nuke stops still have sends unconfirmed. Do not resend: once the hashes in tx_hashes settle, check List a launch's activity events and retry only the part that failed.
422 upstream_failure Solana: not every sale landed, and some may have. Through the execution engine the message goes on with the round that was not sent and the sales that landed before it. Check the balances in Retrieve a launch, then nuke again to sell what is left.
409 launch_migrating EVM: every sale failed because the launch is moving from its curve to its pool. When only some fail, the call answers 200 with ok: true and per-wallet counts. Wait a few seconds, then nuke again.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.nuke(launchId, request) src/lib/proxima/endpoints/launch/launch.ts

Transfer tokens

Bearer JWT
POST /launch/transfer-token/{launch_id}

Sends the launch token from launch wallets to other addresses.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Check before retrying A repeat sends the tokens again. Before resending, check the senders' balances in Retrieve a launch and the launch.transfer_token event in List a launch's activity events; on EVM, resend only the entries listed in failures.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • transfers array<object> Required
    Transfers to make.
    Child attributes 3
    • from string Required
      Launch wallet to send from.
    • recipient string Required
      Address to send to.
    • amount string Required
      Tokens to send, in base units.

Returns 200 OK · application/json

  • ok boolean
    true when every transfer went out. On EVM a 200 can carry false, with the misses in failures.
  • message string
    Human-readable outcome. Solana only.
  • succeeded integer
    EVM only: transfers that went out.
  • failed integer
    EVM only: transfers that did not.
  • tx_hashes array<string>
    EVM only: hashes of the transfers that went out.
  • failures array<object>
    EVM only: one entry per transfer that did not go out, with recipient, sender, amount_token_atomic and error.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
400 bad_request EVM: transfers is empty. Send at least one transfer.
400 bad_request Solana: a recipient is not a valid address. A bad from answers One of the from pubkey is invalid; EVM answers invalid recipient address or invalid from address: <from>. Send valid addresses for the launch's chain in recipient and from.
400 bad_request Solana: a transfer's from and recipient are the same wallet. Send to a different recipient.
500 internal_error Solana: the token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Transfer once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request EVM: the token is not deployed yet. Transfer once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request A from is not one of the launch's wallets. Send from the launch's wallets, as listed by Retrieve a launch.
400 bad_request No transfer names a from wallet, so there is no sender. Set from on every transfer to one of the launch's wallets.
400 bad_request A from wallet lacks the tokens for its transfer, or the SOL or gas to send it. EVM answers from wallet <from> cannot cover its transfer of <amount> (out of tokens or gas), or from wallet <from> holds no tokens or cannot pay for a transfer. Lower the amount or top up the sender, checking its balances in Retrieve a launch.
400 bad_request Every amount is 0. Send at least one transfer with a non-zero amount.
422 unprocessable The execution engine cannot carry this transfer. Nothing was sent. Do not repeat the call unchanged: the reason names what the execution engine cannot carry.
422 unprocessable The execution engine's vault signs some of the senders and not others, and one call cannot mix them. Nothing was sent. Send the transfers of the two wallets the message names in separate calls.
409 lane_pending The execution engine sent a transfer but has not confirmed it, so it can still land. It also answers this, before sending anything, while one of the senders has an earlier send unconfirmed. Do not resend: once the hashes in tx_hashes settle, check List a launch's activity events and retry only the part that failed.
422 upstream_failure Solana: not every transfer landed. Bundles sent before the failing one may have landed. Check the senders' balances in Retrieve a launch, then send again only the transfers that did not land.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.transferTokens(launchId, transferPlan) src/lib/proxima/endpoints/launch/launch.ts

Burn the dev supply

Bearer JWT
POST /launch/burn-dev-supply/{launch_id}

Burns tokens from the dev wallet.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Check before retrying A repeat burns again, and 0 burns whatever is left. Check the dev wallet's balance in Retrieve a launch and look for the launch.burn_dev_supply event in List a launch's activity events first.

Burning is irreversible.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • amount string Required
    Tokens to burn, in base units. 0 burns the whole dev balance.

Returns 200 OK · application/json

  • ok boolean
    true when the request succeeded.
  • message string
    Human-readable outcome. Solana only.
  • signature string
    Transaction signature, or transaction hash on EVM.
  • token_burned string
    EVM only: tokens burned, in base units.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
400 bad_request EVM: amount is missing. Send amount, or 0 to burn the whole dev balance.
500 internal_error Solana: the token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Burn once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request EVM: the token is not deployed yet. Burn once the launch is live, as shown by launch_status in List the license's launches.
500 internal_error Solana: the launch was imported without its dev wallet's key. Burn only on launches whose dev wallet key Proxima holds.
400 bad_request EVM: the dev wallet is watch-only and cannot sign. A launch with no dev wallet answers no dev wallet configured. Burn only on launches whose dev wallet key Proxima holds.
400 bad_request EVM: the dev wallet holds none of the token. Solana answers 200 with the message No tokens to burn instead. Check the dev wallet's balance in Retrieve a launch: there is nothing to burn.
422 unprocessable Solana: amount is more than the dev wallet holds. Lower amount, or send 0 to burn the whole balance.
400 bad_request EVM: amount is more than the dev wallet holds. Lower amount, or send 0 to burn the whole balance.
422 upstream_failure Solana: the burn was not confirmed as landed. Check the dev wallet's balance in Retrieve a launch before burning again.
422 upstream_failure EVM: the burn transaction failed, and the message carries the sender's reason. Check the dev wallet's balance in Retrieve a launch before burning again.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.burnDevSupply(launchId, amount) src/lib/proxima/endpoints/launch/launch.ts

Lock the dev supply

Bearer JWT
POST /launch/lock-token/{launch_id}

Locks tokens from the dev wallet in a Streamflow lock on Solana.

Token
Upgraded session token, bound to a license.
Read-only tokens
Refused with 403 read_only_token.
Retry
Check before retrying A repeat creates a second lock. Look for the launch.lock_token event, which carries the lock's strm_metadata, in List a launch's activity events, and check the dev wallet's balance in Retrieve a launch first.

Path parameters

  • launch_id string Required
    Public ID of the launch.
    Example101482937561204

Body parameters application/json

  • amount string Required
    Tokens to lock, in base units. At least 100000000.
  • period integer Required
    Lock duration, in seconds. At least 60.

Returns 200 OK · application/json

  • ok boolean
    true when the request succeeded.
  • message string
    Human-readable outcome.
  • strm_metadata string
    Streamflow lock account.

Errors

StatusCodeWhen and what to do
400 bad_request launch_id is not a valid launch ID. Pass the launch_id returned when the launch was created, as listed by List the license's launches.
404 not_found No launch with this ID belongs to your license. Check the ID, and that your token is upgraded onto the license that owns the launch.
400 unsupported_chain The launch is not on Solana. Call this endpoint only for Solana launches.
500 internal_error The token is not deployed yet. A launch with no saved plan answers No launch data saved or No launch method saved instead. Lock once the launch is live, as shown by launch_status in List the license's launches.
400 bad_request amount is below 100000000 base units. An amount of 0 answers Invalid lock amount. Lock at least 100000000 base units.
400 bad_request period is below 60 seconds. Lock for at least 60 seconds.
500 internal_error The launch was imported without its dev wallet's key. Lock only on launches whose dev wallet key Proxima holds.
422 unprocessable The dev wallet holds less than amount plus Streamflow's 0.5% fee. Lower amount so it fits the dev balance shown in Retrieve a launch, fee included.
422 unprocessable The dev wallet holds less than the 0.175 SOL the lock needs. Top up the dev wallet to at least 0.175 SOL, then lock again.
422 upstream_failure The lock was not confirmed as landed. Check the dev wallet's balance in Retrieve a launch before locking again, since a second call creates a second lock.

Also the common errors: 401 for a missing or expired session or a base token (license_required), 403 read_only_token and 429 when rate limited.

Web client proxima.launch.lockDevSupply(launchId, amount, period) src/lib/proxima/endpoints/launch/launch.ts