Detail levels
Set detail options inside the subscription's params.
basic
basic is the default on every stream. It contains the fields required to identify and use the event while keeping payloads small.
{
"op": "subscribe",
"id": 1,
"stream": "token_trades",
"params": {
"mint": "DD9e...",
"detail": "basic"
}
}full
full adds the stream-specific fields documented on each stream page:
- creator activity on
launches - liquidity on
migrations - LP mint and first deposit on
pool_creations - pool, aggregator, reserves, fees, compute units, priority fee, and standalone transfers on
token_trades - full route and transaction costs on
wallet_trades - transfer kinds and endpoint types on transfer streams
- volume and trade counts on
candles
Full fields keep a stable shape: a field never disappears from one event to the next. When there is no value, an address comes as null and a list comes as []. What may be empty covers the cases worth knowing about.
full is available from the Pro plan.
Traffic
full adds fields, not events. You receive exactly as many events as on basic, but each one is several times larger, and the subscription's traffic grows with it. If you need one or two of the extra fields, that is worth weighing on a busy token.
includeRaw
includeRaw: true adds the transaction's complete transfer ledger as rawTransfers[].
{
"op": "subscribe",
"id": 1,
"stream": "wallet_transfers",
"params": {
"wallet": "9GXm...",
"detail": "full",
"includeRaw": true
}
}It is available only for token_transfers and wallet_transfers, requires detail: "full", and is available on the Scale plan.
Traffic
includeRaw is the expensive one. It attaches the full ledger of every transaction, so the volume grows a great deal while the number of events does not change at all. Turn it on for a specific job — reconciling transactions, auditing a wallet — rather than on a subscription that runs for days.
Requests outside the key's plan fail with not_on_plan; the feature field is detail_full or include_raw.