Skip to main content
Alpha feature: Token Filters access is gated. Ask the Mobula team to enable it for your account. Until then, use Pulse; it works the same way for the same view/filter workflow.
Pulse remains the production-ready path while Token Filters is in alpha. This guide is for teams that already have Token Filters enabled or are preparing a migration.

Migration Overview

Token Filters introduces several breaking changes that improve the developer experience:

Step 1: Update Connection Flow

Pulse V2 (Old Way)

Token Filters (New Way)

Important: Always send the full mode and views payload via WebSocket. Do NOT send just a subscriptionId - the WebSocket subscription is stateless and requires the complete configuration.

Step 2: Update Mode Parameter

Pulse V2

Token Filters

Step 3: Update Filter Field Names

Token Filters uses consistent camelCase for all filter fields. Here’s the mapping:

Price & Market Data

Volume Fields

Price Change Fields

Trade & Participant Fields

Holdings Fields

Trader Category Fields

Organic Fields

Bonding & Timestamp Fields

Metadata Fields

Special Filters

Step 4: Handle Partial Updates

Pulse V2 (Full Updates)

Token Filters (Partial Updates)

Important: Token Filters partial updates only include fields that changed. You MUST merge them with your existing state, not replace the entire object.

Step 5: Handle Remove Messages

Pulse V2 (Pipe-separated String)

Token Filters (Structured Object)

Step 6: Remove Sync Message Handling

Pulse V2

Token Filters

Step 7: Update Preset Models

Pulse V2

Token Filters

Model Comparison

New Token Filters Models

New Capabilities

Token Filters keeps the Pulse-style view/filter workflow, and adds a few alpha-only controls:

Complete Migration Example

Pulse V2 Code (Before)

Token Filters Code (After)

Checklist

Use this checklist to ensure complete migration:
  • Update REST endpoint from /api/2/pulse to /api/2/token/filters
  • Update connection flow to REST API init + WebSocket subscribe
  • Change type from pulse-v2 to token-filters
  • Change assetMode: true/false to mode: "token"/"market"
  • Update all filter field names to camelCase
  • Update all sortBy field names to camelCase
  • Implement partial update handling (merge, don’t replace)
  • Update remove message handling for structured objects
  • Remove sync message handling (no longer sent)
  • Remove init message handling (handled by REST)
  • Test with real data

Need Help?

Support

Telegram

Support

Slack

Need help?

Email