Skip to main content
The Bloom API lets you drive trading and token launches programmatically using a personal API key:
  • Swaps: execute buys and sells across one or more of your wallets — or, with wallets omitted, across your default trading wallets — with optional take-profit, stop-loss, trailing, time-based, and dev-sell auto-orders.
  • Token deploys: launch new tokens on supported launchpads — pump.fun, Bags and Bonk on Solana, and a per-chain set on EVM — with bundled buys and post-deploy distributions.
  • Wallets: list the wallets on the account, so an integration can discover addresses instead of asking for them.

​
Base URL

All requests go to a Bloom API host under the /api/v1 prefix. Solana is served from two regions — pick the one nearer you:
Both regions serve /api/v1/deploy as well, and both are backed by the same account, wallets, and rate-limit budget — the only difference is network latency. See Regions. For EVM chains, use https://evm.bloombot.app:
Every request is authenticated with a Bearer token. One EVM key covers every EVM chain, but Solana and EVM keys are not interchangeable. EVM requests accept a chain field, which works differently on each endpoint:
  • On a swap, it is optional and names the chain to trade on (eth, bsc, base, rbh, or arc). Omit it and the token is resolved across chains automatically.
  • On a deploy, it selects one of rbh, bsc, arc or ink, and omitting it defaults to rbh rather than searching.
See Chains and quote assets for the per-chain quote assets and how fee fields are denominated, and Deploy a token for the launchpads on each chain.

Quickstart

Create a key and make your first swap in a few minutes.

API Reference

Full request and response schemas for /swap and /deploy.

Authentication

How API keys work: format, limits, and revocation.

Auto-orders

Attach exit strategies and dev-sells to a trade.

Chains and quote assets

The chain field, per-chain quote assets, and EVM fee units.

Builder fees

Earn a share of the swaps your integration sends.