Skip to main content
On the chains we index, Serialized Data maps the market-data surface of Mobula, Codex and Birdeye: token details, prices, candles, trades, holders, wallet intelligence, launchpad feeds and live streams. Each tab ends with the main surfaces that are not carried over.
Mobula’s market-data surfaces map below, on our chains; the main ones that do not carry over are listed at the end of this tab. A Mobula integration moves with minimal relearning: auth is the same convention (raw API key in the Authorization header) and the credit model is aligned: pay as you go, or a monthly Growth plan with credits included.

Conventions that differ

Endpoint map

Security fields

GET /api/2/token/security field by field, on GET/POST /v1/token/security:

Security on Pulse and Screener rows

The security object of pulse rows and screener results, and the security.* filters, map to the risk block of every GET /v1/pulse, GET /v1/screener row and every pulse and screener stream row. Filters and sorts on risk.* are served by the Screener and the Pulse, REST and streams:The holder fields of pulse rows map to the row fields of the same names as /v1/token/security, on every GET /v1/pulse, GET /v1/screener and GET /v1/search row and every pulse and screener stream row. They filter and sort on the Pulse and the Screener, REST and streams, and filter the search:

Streams

The protocol: one wss endpoint (wss://ws.serialized.xyz/v1/stream), auth as the first frame, then additive subscriptions with explicit acks and per-id unsubscribe. Event payloads reuse our REST shapes, so your parser is already written. Mobula bills 1 credit per minute of connection plus what each update consumes; here an open connection is free, a live view (Pulse, Screener) costs 1 credit per message, and the other channels cost 1 credit per element with on-chain activity in each message: a pool that traded, a token, a candle series, a wallet on one chain (Streams billing). maxUpdatesPerMinute is accepted on every subscription, next to our updatePeriod. Every channel is open to every key.

Price webhooks

Mobula’s GraphQL API (in alpha) sends price webhooks (createWebhooks with a TOKEN_PRICE_EVENT webhook, a level on priceUsd). Here one price webhook is your endpoint and its secret, and carries your triggers (1,000 active per account by default, more on request), each one a token and a level in USD or in the chain’s native coin: create it once, then add and remove triggers.Pricing: 1 credit per trigger sent to your URL; managing webhooks and triggers is free. Mobula’s REST webhooks of swaps and transfers (POST /api/1/webhook) are not served as webhooks: follow wallets live on the wallet-trades and wallet-balances channels.Not carried over: the chains we do not index (Supported chains lists ours), execution (swaps, bridges, perps), perps and CeFi market data (funding rates), prediction markets, NFT, wallet DeFi positions, the holders stream and first buyers. If one of these blocks your migration, tell us.
Whatever you come from: send us your current endpoint list and we will return the exact mapping for your integration, run a side-by-side accuracy pass with you, and stay on call during the switch.