/v1/launch-token
Create new token with AMM
Payload
https://api.xrpl.to/v1/launch-token{ currencyCode, tokenSupply, ammXrpAmount, name, origin, user, antiSnipe?, shield? (default true), imageData?, domain?, description?, telegram?, twitter?, userCheckAmount?, platformRetentionPercent?, ammTradingFee?, bundleRecipients?[], vesting? }
curl -X POST 'https://api.xrpl.to/v1/launch-token'
Response
What it does
Create new token with AMM
- Notes
- Every wallet the launch will send to (userAddress, bundleRecipients[].address) is checked on the ledger first. One that cannot receive is refused with 400 "Wallet cannot receive" before a session exists: not activated, requires a destination tag, refuses checks, or (vesting) refuses trust lines. The anti-snipe shield is on by default, vesting included; only antiSnipe (the gated window) cannot be combined with vesting.