Skip to main content
POST
POST /v1/wallet/funding · 1 credit per 25 wallets Batch twin: the first funder of up to 100 {chain, wallet} items in one call, EVM and Solana mixed freely. Every item names its chain (the first funder is read per chain). The response comes back 200 in input order, one slot per wallet: { data }, exactly the body of GET /v1/wallet/funding for that wallet (data: null when no funder is known, as on the GET), or { error: { code, message } } for that wallet alone (unknown chain, malformed address), never a missing slot. One bad wallet never costs you the rest of the lot. Billed 1 credit per 25 wallets served: 1 to 25 wallets cost 1 credit, 26 to 50 cost 2; the same address requested on several chains counts as one wallet.
A slot’s data is exactly what GET /v1/wallet/funding returns for that wallet: funder, fundedAt, txHash, amountNative and funderTag; see that page for the fields.

Authorizations

Authorization
string
header
required

Your raw API key (not needed on the demo server).

Body

application/json
items
object[]
required

[{ "chain": "…", "wallet": "…" }] - 1 to 100 wallets, chain required on each (the first funder is read per chain).

Required array length: 1 - 100 elements
Example:

Response

200

Standard { data, meta } envelope.