API reference

Step 1GET/launch/termsLaunch#

Launch step 1: the terms message to sign

`version`, `signedAt` and `message`: sign `message` (UTF-8, ed25519) with the wallet within 10 minutes, then POST it back. Once per wallet per terms version.

curl "https://weball.fun/api/v1/launch/terms?wallet=<wallet>"

Step 2POST/launch/termsLaunch#

Launch step 1: accept the terms

Body: `{ wallet, version, signedAt, signature }`: `signature` is the base64 ed25519 signature of `message`.

`{ accepted: true }`.

curl -X POST "https://weball.fun/api/v1/launch/terms" \
  -H 'content-type: application/json' \
  -d '{ … }'

Step 3POST/launch/prepareLaunch#

Launch step 2: prepare a coin (free for a limited time)

Body: `{ creator, mint, name, ticker, description?, socials?: { x?, telegram?, website? }, image? (base64), mode: "holder" | "creator", feeBps, basket?: [{ mint, weight }], recipients?: [{ wallet, pct, label? }], buyBps?, rollIn?, hooks?: ["anti-sniper"] }`. `mint` is a fresh keypair’s address you hold, used only when our address pool is empty.

Validates and records the launch, then returns the unsigned transaction. Free for a limited time; a wallet may prepare 5 launches an hour. SOL coins without a creator lock for now. With `hooks` (live ids from /hooks, where `open`), the coin is a Token-2022 token paired with SOL. `mint`, `pool`, `transaction` (base64, unsigned), `lastValidBlockHeight`, `buy` and `mintSource`. Sign `transaction` with `creator`, and also with your `mint` keypair when `mintSource` is "browser" (when it is "pool" we add the mint signature at submit). Then POST it to /launch/submit before it expires.

curl -X POST "https://weball.fun/api/v1/launch/prepare" \
  -H 'content-type: application/json' \
  -d '{ … }'

Step 4POST/launch/submitLaunch#

Launch step 3: send the signed launch

Body: `{ mint, transaction }`: the signed transaction, base64.

`{ status: "confirmed", signature, result }`, or `{ status: "pending", signature }`: then POST /launch/confirm with the signature. Never sign and send it again.

curl -X POST "https://weball.fun/api/v1/launch/submit" \
  -H 'content-type: application/json' \
  -d '{ … }'

Step 5POST/launch/confirmLaunch#

Launch step 4: confirm a pending launch

Body: `{ mint, signature }`.

The launch once confirmed on chain; a 409 while it hasn’t landed yet (try again shortly).

curl -X POST "https://weball.fun/api/v1/launch/confirm" \
  -H 'content-type: application/json' \
  -d '{ … }'

Step 6POST/launch/pump/prepareLaunch#

Launch on pump.fun: prepare a coin (free for a limited time)

Body: `{ creator, mint, name, ticker, image (base64), description?, quoteMint? (the pair: SOL by default, USDC or a token pump.fun lists, GET /api/pump/quotes), holdersPaid?: "pair" | "basket", basket?: [{ mint, weight }], buyLamports? (string; SOL pairs only, up to 10% of supply), socials?: { website?, x?, telegram? } }`. `mint` is a fresh keypair’s address you hold: pump.fun creates the coin there.

Validates and records a pump.fun launch, then returns its unsigned transactions. Free for a limited time; a wallet may prepare 5 launches an hour (with /launch/prepare). Accept the terms first (/launch/terms). Of every creator fee: holders 70%, WeBall 12%, WeBall AI 3%, $BALL bought and burned 10%, the creator's referrer 5% (else $BALL liquidity), locked at launch. `mint`, `transactions` (one or two base64 unsigned v0 transactions: the coin and any first buy, then the fee split), `buyTokens`, `buyMaxLamports` and `sponsored` (true: WeBall pays the launch costs, within 1 SOL a day and 5 a wallet a day for a wallet holding 0.05 SOL; its sponsor is the fee payer and signs at submit, so leave its signature empty). Sign every transaction with `creator`, sign the first with your `mint` keypair too, then POST them all, in order, to /launch/pump/submit before they expire. Wallets may add compute-budget and Lighthouse instructions; anything else is refused.

curl -X POST "https://weball.fun/api/v1/launch/pump/prepare" \
  -H 'content-type: application/json' \
  -d '{ … }'

Step 7POST/launch/pump/submitLaunch#

Launch on pump.fun: send the signed launch

Body: `{ mint, transactions: [base64, …] }`: every transaction prepare returned, signed, in order.

`{ status: "confirmed", signature, result }`, or `{ status: "pending", signature }`: then poll GET /launch/pump/status. Never sign and send them again.

curl -X POST "https://weball.fun/api/v1/launch/pump/submit" \
  -H 'content-type: application/json' \
  -d '{ … }'

Step 8GET/launch/pump/statusLaunch#

Launch on pump.fun: where a launch is

`{ mint, status: "prepared" | "sending" | "confirmed" | "abandoned", page }`: `page` is the coin’s page once it’s confirmed.

curl "https://weball.fun/api/v1/launch/pump/status?mint=<mint>"

POST/webhooks/createWebhooks#

Create a webhook

Body: `{ wallet, time, signature, url, events: string[], mints?: string[] }`. Message fields: `URL: <url>`, `Events: <comma list>`, `Coins: <comma list or all>`.

A signed POST to `url` for each event: `coin.launched`, `coin.graduated`, `payout.paid`. Up to 5 webhooks per wallet, each for every coin or up to 20. Signed by the owner wallet: `wallet`, `time` (ISO, within 5 minutes) and `signature` (base64 ed25519 over the exact message: lines `WeBall webhooks`, `Action: <action>`, `Wallet: <wallet>`, then the action’s fields, then `Time: <time>`; see /developers#webhooks). `{ webhook, secret }` (201). Keep `secret`: it is shown only now, and every delivery carries `WeBall-Signature: t=<unix>,v1=<hex HMAC-SHA256 of "<t>.<body>">` made with it.

curl -X POST "https://weball.fun/api/v1/webhooks/create" \
  -H 'content-type: application/json' \
  -d '{ … }'

POST/webhooks/listWebhooks#

List your webhooks

Body: `{ wallet, time, signature }`.

Signed by the owner wallet: `wallet`, `time` (ISO, within 5 minutes) and `signature` (base64 ed25519 over the exact message: lines `WeBall webhooks`, `Action: <action>`, `Wallet: <wallet>`, then the action’s fields, then `Time: <time>`; see /developers#webhooks). `{ webhooks: [{ id, url, events, mints, status, createdAt, lastSuccessAt, failingSince, pausedAt, deliveries7d }] }`.

curl -X POST "https://weball.fun/api/v1/webhooks/list" \
  -H 'content-type: application/json' \
  -d '{ … }'

POST/webhooks/deleteWebhooks#

Delete a webhook

Body: `{ wallet, time, signature, id }`. Message field: `Webhook: <id>`.

Signed by the owner wallet: `wallet`, `time` (ISO, within 5 minutes) and `signature` (base64 ed25519 over the exact message: lines `WeBall webhooks`, `Action: <action>`, `Wallet: <wallet>`, then the action’s fields, then `Time: <time>`; see /developers#webhooks). `{ deleted: id }`. Nothing more is sent to it, including retries already queued.

curl -X POST "https://weball.fun/api/v1/webhooks/delete" \
  -H 'content-type: application/json' \
  -d '{ … }'

POST/webhooks/enableWebhooks#

Re-enable a paused webhook

Body: `{ wallet, time, signature, id }`. Message field: `Webhook: <id>`.

A webhook whose deliveries all fail for 3 days is paused. Signed by the owner wallet: `wallet`, `time` (ISO, within 5 minutes) and `signature` (base64 ed25519 over the exact message: lines `WeBall webhooks`, `Action: <action>`, `Wallet: <wallet>`, then the action’s fields, then `Time: <time>`; see /developers#webhooks). `{ webhook }`, active again; events from now on are delivered.

curl -X POST "https://weball.fun/api/v1/webhooks/enable" \
  -H 'content-type: application/json' \
  -d '{ … }'

POST/webhooks/testWebhooks#

Send a test ping

Body: `{ wallet, time, signature, id }`. Message field: `Webhook: <id>`.

Sends one `webhook.test` event now, signed like a real one; at most one every 30 seconds per webhook. Signed by the owner wallet: `wallet`, `time` (ISO, within 5 minutes) and `signature` (base64 ed25519 over the exact message: lines `WeBall webhooks`, `Action: <action>`, `Wallet: <wallet>`, then the action’s fields, then `Time: <time>`; see /developers#webhooks). `{ delivered, status, error }`: whether your URL answered 2xx.

curl -X POST "https://weball.fun/api/v1/webhooks/test" \
  -H 'content-type: application/json' \
  -d '{ … }'