Skip to main content
POST
cURL
Use this for a follow list, an alert check, or a leaderboard page where you already hold the addresses. Each row is the same shape as Trader. For one wallet, or for a conditional read with an ETag, use the single route instead.

Parameters

Both fields go in the JSON request body.

Key response fields

Budget

Batch items have their own budget of 2,500 units a minute, separate from the request budget. Every item is reserved before any of them runs, so a request that would go over the budget answers 429 and runs nothing. Read Retry-After, wait that long, and send the same request again. 100 requests of 25 items each is exactly 2,500 items, so the 100 requests a minute budget runs out first. Batching is never the more expensive choice.

Example

What it does not return

  • Part of a batch on a 429. No item ran, so nothing was charged and nothing was returned.
  • A 400 for a wallet 0xinsider does not track yet. That row is ok with sync_status set to unknown, the same as on the single route. An empty or blank string is an error row with code bad_request.
  • A non-200 when some rows fail. Read meta.failed_items and each row’s status.
  • An ETag. Conditional reads live on Trader.
  • More than 25 rows. An empty array, or 26 or more wallets, answers 400 for the whole request and runs nothing.

Authorizations

Authorization
string
header
required

Legacy default or named integration API key, or OAuth 2.1 access token, in the Authorization header as Bearer oxi_sk_live_... or Bearer oxi_at_.... Default keys retain full access; integration keys are limited to their approved read, webhooks, export and usage scopes and expire within 90 days. All credentials share the owner's account limits. Data calls require an active Pro subscription and return live data. A 401 carries WWW-Authenticate: Bearer resource_metadata="https://api.0xinsider.com/.well-known/oauth-protected-resource" (RFC 6750 section 3, RFC 9728).

Headers

X-Query-Validation
enum<string>

Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.

Available options:
strict

Body

application/json

Batch trader lookup request. Supply 1-25 wallet addresses, usernames, trd_-prefixed IDs, or integer trader IDs. Optional expand flags apply to every item.

traders
string[]
required

Trader identities to resolve in input order.

Required array length: 1 - 25 elements
expand
enum<string>[]

Shared expand flags applied to every trader item.

Available options:
strategy,
categories,
quant_metrics,
trust

Response

Ordered batch trader results

object
string
required
Allowed value: "trader_batch"
data
object[]
required
meta
object
required