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
  • sign the returned transactions and broadcast them yourself. Nothing to submit back
  • large groups come back as several transactions, so handle every entry in transactions
Find batchable tokens with Get tokens and hasBundler=true. See the Split flow for the full sequence.

Choosing a transaction format

Solana has more than one transaction format. Use txVersion to choose which one you get back. If you are not sure, leave it out and you get legacy. Why use v1? Each transaction pays 3 times more SOL deposits, so the user signs fewer times. For example, 50 SOL deposits take 3 transactions with legacy but only 1 with v1. Token batches stay at 10 in every format: creating the receiving token accounts hits a Solana limit before the size limit does. When not to use v1: if the wallet or library that signs does not support it, signing fails. @solana/web3.js 1.x can read a v1 transaction but cannot sign it. To check support, see Solana’s Larger Transaction Sizes guide:
  • Libraries — the “Support for V1 Transactions” table lists the minimum version of each Solana library
  • Wallets — a wallet that can sign v1 lists 1 in its supportedTransactionVersions. Check it before you request txVersion=v1
The response’s txVersion field tells you which format you got.

Signing and sending

  • legacy — decode with Transaction.from(Buffer.from(txData.data, "base64")) from @solana/web3.js
  • v0 — decode with VersionedTransaction.deserialize(Buffer.from(txData.data, "base64")) from @solana/web3.js
  • v1 — decode and sign with a library that supports v1, then send with encoding: "base64". A v1 transaction can be larger than 1232 bytes, and base58 encoding cannot carry it. See Solana’s Larger Transaction Sizes guide for examples

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 Split 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 divided 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.