Start with an intent
Use your Bitbank API token in the Authorization header. Never put API tokens or wallet keys in a URL. The API never needs a wallet private key.
curl -X POST https://bitbank.nz/api/v1/launchpad/intents \
-H "Authorization: Bearer $BITBANK_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: project-launch-001" \
--data '{
"name": "My project", "symbol": "BUILD",
"description": "A community for builders",
"image_uri": "ipfs://YOUR_PINNED_IMAGE_CID",
"website": "https://example.com", "chain_id": 46630,
"fee_bps": 100,
"recipients": [{
"provider": "wallet", "handle": "",
"wallet": "0x1111111111111111111111111111111111111111",
"share_bps": 10000
}]
}'
A successful response is 201 with status: "draft". Repeating the same payload and key returns the same draft; changing the payload returns 409. No transaction is sent. Upload artwork first with POST /images (multipart file); the response carries an ipfs:// URI when pinning is configured and a CDN url when bucket storage is configured.
Download OpenAPI specification →0.10% to Bitbank. The rest to collaborators.
The default pool fee is 1.00% of trading volume: 0.10% protocol share plus 0.90% for creator-selected recipients. A draft may choose fee_bps of 100, 50, 30 or 10. Bitbank keeps 0.10% at every tier; the collaborator share is the remainder, so 10 basis points leaves nothing for collaborators and needs no recipients.
The deployed contracts currently enforce the 1.00% tier. Drafts at other tiers are stored and validated but cannot be launched until the locker supports them. 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.
API v1
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 WETH and sells receive WETH. Approvals, 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.
People have handles. Payouts have wallets.
GitHub and X use OAuth with PKCE and a one-time browser-bound state. Accounts are identified by stable provider IDs. Sign in first, then use the connection buttons to link another provider.
Social labels on drafts do not authorize payouts. Each recipient needs an explicit EVM wallet, and connecting a wallet in the browser is not proof of ownership. Social-handle-only claims and wallet identity attestations are not enabled.
What is ready today
Discovery, launch drafts, fee allocation, account connections and this API reference. Social login needs provider credentials; image uploads need bucket or pinning credentials. Unsigned native launch, trade and claim adapters are implemented and require a verified deployment manifest. Each request checks the chain and deployed code, then simulates the transaction.
Robinhood Chain is the first target. Solana support is a future adapter; there is no implied bridge or duplicate token. Companion contract source: bitbanknz/bitbankcontracts ↗.
