Skip to main content
GET
Get batch transaction
  • every order must send the same token — all native SOL, or all the same SPL token. Mixing SOL with an SPL token is rejected
  • up to 10 deposits per batch
  • sign the returned transaction and broadcast it yourself. Nothing to submit back
  • large groups come back as several batches, so handle every entry in transactions
Find batchable tokens with Get tokens and hasBundler=true. See the multi-swap flow for the full sequence.

Authorizations

Authorization
string
header
required

Send Authorization: <ApiKey>:<ApiSecret> — joined by a colon, raw. No Bearer prefix, no base64.

Get your credentials

Path Parameters

multiId
string
required

The multi exchange group ID

Maximum string length: 64

Query Parameters

sender
string
required

Wallet address that will sign and fund the transaction(s)

Minimum string length: 1
houdiniIds
string
txVersion
enum<string>

Transaction format to build. If you are not sure, leave it out.

  • legacy (default): works with every Solana wallet
  • v0: same capacity as legacy. Use it if your code expects a versioned transaction
  • v1: fits 3 times more SOL deposits in one transaction, so the user signs fewer times. Token batches stay the same size. Use it only if the wallet or library that signs supports v1. See Choosing a transaction format
Available options:
legacy,
v0,
v1

Response

Success

multiId
string
required

The group these transactions fund.

chain
string
required

Chain kind of the from token (e.g. "solana", "evm")

transactions
object[]
required

One entry per batch. A group larger than the per-chain batch limit is split across several.

txVersion
enum<string>

Solana only. Format of every transaction in transactions. Matches the txVersion you requested, or legacy if you did not set one.

Available options:
legacy,
v0,
v1
depositNeeded
string

Native coin the smart account still needs before you can submit, in wei. "0" means it is already funded.

saCurrentBalance
string

Native coin the smart account holds right now, in wei. The account is owned by the sender wallet, so this balance stays under the user's control.