Skip to main content
Mobula’s spot data API, mapped field by field: requests, authentication, chain IDs, streams, and every field on the token object.

Key differences

Endpoints

Streams

Mobula sends the API key inside each subscribe payload. Here, the key goes on the WebSocket handshake once, and every subscribe frame uses the same shape: {"action": "subscribe", "channel": …, "filters": …}. See Connecting to streams.

Token object

Mobula field names below are from its GET /api/2/token/details response.

Identity and market

Trailing windows

Mobula fuses the window into each field name. Here, windows are keys under stats. The windows differ:

Holders

The two APIs classify wallets with their own rules, so the same field can read differently. See the glossary for the rules here.

Security

Launchpad and metadata

Checklist

  • Move the key to Authorization: Bearer, on REST requests and the stream handshake.
  • Replace chain IDs with slugs.
  • Move token addresses from query parameters into the path.
  • Parse amounts as decimal strings, and read .usd for dollar values.
  • Read trailing windows from stats.
  • Switch error handling to error.code. See Errors, limits and retries.
  • Move stream subscriptions to the action / channel / filters frame.