Skip to main content
GET
List wallets
This endpoint does not count against any rate-limit window — it is an in-memory lookup — so an integration can call it as often as it likes. See Rate limits.

Why list wallets

An integration built on the Bloom API used to need two things from each user: an API key and a wallet address — with no way to check that the address was actually one of theirs until a swap failed with WALLET_NOT_OWNED. This endpoint closes that gap: ask for the key, then read the wallets it is bound to. Every address returned is accepted by wallets[].address on a swap. The spot_active flag tells you which wallets Bloom itself trades from — and therefore which ones a swap that omits wallets will run on.
A wallet’s spot_active flag is whatever the user last set in Bloom Manager or the bot; it can change between calls. If your integration must trade from one specific wallet, name it in wallets rather than relying on the default.

Authorizations

Authorization
string
header
required

Your Bloom API key, e.g. Authorization: Bearer blm_sol_live_…. Create one in Bloom Manager → Manage API Keys.

Response

Your wallets.

success
boolean
required
Example:

true

data
object
required