201 returns a draft. Reuse the same idempotency key and payload to retrieve it; a changed payload returns 409. No transaction is sent.
Upload artwork with POST /images (multipart file) for an IPFS URI or CDN URL.
Trading FAQ
How do swaps, approvals, and quotes work?
ETH⇄WETH wraps run in your wallet. Buy launch tokens with ETH in one transaction; sells pay out ETH after a one-time token approval. Quotes are enforced onchain for 60 seconds.
Try the API
Run a request against this server.
0.10% to Bitbank. The rest to collaborators.
The pool fee is 1.00% of trading volume: 0.10% protocol share plus 0.90% for creator-selected recipients. Use fee_bps: 100 for this deployed fee tier.
Launches are enabled on the deployed factory and locker, with no platform launch charge. Recipient share_bps values divide the collaborator portion and must total 10,000. Gas, launch charges, price impact and slippage are separate. The existing Pons token retains its original policy.
Deployed contracts (Robinhood Chain, chain id 4663)
Runtime code hashes are pinned in the server manifest and re-verified on every transaction request. Contract source: bitbanknz/bitbankcontracts ↗.
API v1
Method & endpoint
Purpose
Статус
GET/config
Fees and capabilities
Available
GET/tokens
Confirmed recent launches and external Bitbank token
Available
GET/analytics
Census and market coverage
Available
GET/intents
Your latest 50 drafts
Authenticated
POST/intents
Validate and save a draft
Authenticated
POST/images
Image upload to Bitbank storage and IPFS
Requires storage configuration
GET/connections
Your linked identities
Authenticated
POST/splits/transactions
Unsigned collaborator splitter deployment
Requires verified deployment
POST/launch/transactions
Unsigned launch
Requires verified deployment
POST/trade/quote
Executable trade quote
Requires verified deployment
POST/trade/transactions
Unsigned swap
Requires verified deployment
GET/fees/positions
Claimable balances
Requires verified deployment
POST/fees/claim-transactions
Unsigned fee claim
Requires verified deployment
For a native launch, deploy a splitter with /splits/transactions, wait for its receipt, then pass its address to /launch/transactions. Trade amounts are integer base units; buys spend native ETH and sells receive native ETH. A sell needs one unlimited router approval per token; swaps and staged claims each require a separate signature and successful receipt.
All paths use /api/v1/launchpad. Errors have {"error":{"code":"…","message":"…"}}. Respect HTTP status codes; retry 503 responses with backoff, never blindly resubmit signed transactions.
