Filter Reference & System Metadata: For complete filter documentation including all available fields, operators, and examples, see Filter Details. All available factory names and pool types can be found at: https://api.mobula.io/api/1/system-metadata
Pool-Based Version Available: The Pool-Based version for pool statistics is available here: Pulse Stream V2 Pool-Based
This endpoint is only available to Growth and Enterprise plans.
Real-time vs HTTP
🔗 GET Method
Available in HTTP queriesUse the same filtering system in HTTP GET requests for simple queries.
📝 POST Method
Available in HTTP queriesUse the same filtering system in HTTP POST requests for advanced configurations.
🚀 V1 Stream
Legacy WebSocket APIPrevious version with single payload architecture.
Overview
Pulse Stream V2 Token-Based introduces a new payload-based architecture that allows you to manage multiple views simultaneously with enhanced control over token data flow and view management. This version focuses on token statistics and analytics rather than pool-based data.Key Features
- Token-Based Analytics: Subscribe to token statistics and real-time data
- Multiple Views: Subscribe to multiple custom views simultaneously
- Payload-based Architecture: Each view receives its own payload with view-specific data
- View Management: Pause/unpause individual views without disconnecting
- Enhanced Filtering: Advanced filtering capabilities with real-time token updates
- Personalized IDs: Track multiple client sessions with custom identifiers
- Asset Mode: Focused on token statistics rather than pool data
Endpoint Details
- URL: wss://pulse-v2-api.mobula.io
- Message format: JSON string
- Architecture: Payload-based with view management
- Mode: Token-based (assetMode: true)
Basic Usage
Default Model Configuration (Token-Based)
The simplest way to get started is using the default model in asset mode, which automatically generates three predefined views for token analytics:-
new
- New tokens not yet bonded- Filters:
bonded: false
,source: { not: null }
- Sort:
created_at
descending - Limit: 50 tokens
- Filters:
-
bonding
- Tokens in bonding phase- Filters:
bonding_percentage: { lt: 100 }
,volume_1h: { gte: 10 }
,bonded: false
- Sort:
bonding_percentage
descending - Limit: 50 tokens
- Filters:
-
bonded
- Fully bonded tokens- Filters:
bonded: true
- Sort:
bonded_at
descending - Limit: 50 tokens
- Filters:
Custom Views Configuration (Token-Based)
For more control over token analytics, you can define custom views:Token Data Model
TokenDataSchema Structure
The Token-Based mode provides access to comprehensive token statistics following theTokenDataSchema
structure:
Available Token Statistics
The Token-Based mode provides access to comprehensive token statistics from theTokensStatsRealTime
schema:
Price Data
latest_price
: Current token priceprice_1min_ago
,price_5min_ago
,price_1h_ago
,price_4h_ago
,price_6h_ago
,price_12h_ago
,price_24h_ago
: Historical pricesprice_change_1min
,price_change_5min
,price_change_1h
,price_change_4h
,price_change_6h
,price_change_12h
,price_change_24h
: Price changes
Market Data
market_cap
: Current market capitalizationlatest_market_cap
: Latest market cap calculationholders_count
: Number of token holdersliquidity
: Available liquidity
Volume & Trading Data
volume_1min
,volume_5min
,volume_15min
,volume_1h
,volume_4h
,volume_6h
,volume_12h
,volume_24h
: Volume metricsvolume_buy_1min
throughvolume_buy_24h
: Buy volume metricsvolume_sell_1min
throughvolume_sell_24h
: Sell volume metricstrades_1min
throughtrades_24h
: Trade count metricsbuys_1min
throughbuys_24h
: Buy transaction countssells_1min
throughsells_24h
: Sell transaction counts
Participant Analytics
buyers_1min
throughbuyers_24h
: Unique buyer countssellers_1min
throughsellers_24h
: Unique seller countstraders_1min
throughtraders_24h
: Unique trader countsfees_paid_1min
throughfees_paid_24h
: Fees paid metrics
Organic Trading Data (Excluding Bot Activity)
The organic metrics provide cleaner data by filtering out bot activity and MEV transactions: Organic Volume Metrics:organic_volume_1min
,organic_volume_5min
,organic_volume_15min
,organic_volume_1h
,organic_volume_4h
,organic_volume_6h
,organic_volume_12h
,organic_volume_24h
: Total organic volumeorganic_volume_buy_1min
throughorganic_volume_buy_24h
: Organic buy volumeorganic_volume_sell_1min
throughorganic_volume_sell_24h
: Organic sell volume
organic_trades_1min
throughorganic_trades_24h
: Organic trade countsorganic_buys_1min
throughorganic_buys_24h
: Organic buy transaction countsorganic_sells_1min
throughorganic_sells_24h
: Organic sell transaction counts
organic_buyers_1min
throughorganic_buyers_24h
: Unique organic buyer countsorganic_sellers_1min
throughorganic_sellers_24h
: Unique organic seller countsorganic_traders_1min
throughorganic_traders_24h
: Unique organic trader counts
Token Information
source
: Token source/factoryfactory
: Factory addresspoolAddress
: Associated pool addressdeployer
: Token deployer addresstokenSymbol
: Token symboltokenName
: Token namedexscreenerListed
: Whether listed on DexScreener
Social & Security Data
twitter
: Twitter handletelegram
: Telegram linkwebsite
: Website URLothers
: Other social linkssecurity
: Security analysis datatwitterRenameCount
: Twitter rename counttwitterRenameHistory
: Twitter rename history
Bonding & Migration Data
bonded
: Whether token is bondedbonding_percentage
: Bonding curve completion percentagemigrated_at
: Migration timestampbonded_at
: Bonding completion timestamp (from pool with bonding curve address when bonded=true)liquidityMax
: Maximum liquidity reached
Holdings Analysis
dev_holdings_percentage
: Developer holdings percentagebundlers_holdings_percentage
: Bundler holdings percentageinsiders_holdings_percentage
: Insider holdings percentagesnipers_holdings_percentage
: Sniper holdings percentagepro_traders_holdings_percentage
: Professional trader holdings percentagetop_10_holdings_percentage
: Top 10 holders percentagetop_50_holdings_percentage
: Top 50 holders percentagetop_100_holdings_percentage
: Top 100 holders percentagetop_200_holdings_percentage
: Top 200 holders percentagedeployer_migrations_count
: Deployer migration counttwitter_reuses_count
: Twitter reuse count
Enhanced Liquidity & Pool Data
liquidityMax
: Maximum liquidity across all pools for the tokenpreBondingFactory
: Factory address before bonding completionpoolAddress
: Primary pool address (highest volume pool)
Timestamps
latest_trade_date
: Last trade timestampcreated_at
: Token creation timestamp
Available Filter Fields
Based on theTokensStatsRealTime
schema, you can filter on the following fields:
Price & Market Data
price
: Current token pricemarket_cap
: Market capitalizationlatest_price
: Latest pricelatest_market_cap
: Latest market capholders_count
: Number of token holdersliquidity
: Available liquidity
Volume & Trading Data
volume_1min
throughvolume_24h
: Volume metrics for different timeframesvolume_buy_1min
throughvolume_buy_24h
: Buy volume metricsvolume_sell_1min
throughvolume_sell_24h
: Sell volume metricstrades_1min
throughtrades_24h
: Trade count metricsbuys_1min
throughbuys_24h
: Buy transaction countssells_1min
throughsells_24h
: Sell transaction counts
Participant Analytics
buyers_1min
throughbuyers_24h
: Unique buyer countssellers_1min
throughsellers_24h
: Unique seller countstraders_1min
throughtraders_24h
: Unique trader countsfees_paid_1min
throughfees_paid_24h
: Fees paid metrics
Organic Trading Data
organic_volume_1min
throughorganic_volume_24h
: Organic volume metricsorganic_trades_1min
throughorganic_trades_24h
: Organic trade countsorganic_buyers_1min
throughorganic_buyers_24h
: Organic buyer countsorganic_sellers_1min
throughorganic_sellers_24h
: Organic seller countsorganic_traders_1min
throughorganic_traders_24h
: Organic trader counts
Holdings Analysis
dev_holdings_percentage
: Developer holdings percentageinsiders_holdings_percentage
: Insider holdings percentagesnipers_holdings_percentage
: Sniper holdings percentagebundlers_holdings_percentage
: Bundler holdings percentagepro_traders_holdings_percentage
: Professional trader holdings percentagetop_10_holdings_percentage
: Top 10 holders percentagetop_50_holdings_percentage
: Top 50 holders percentagetop_100_holdings_percentage
: Top 100 holders percentagetop_200_holdings_percentage
: Top 200 holders percentage
Bonding & Migration Data
bonding_percentage
: Bonding curve completion percentagedeployer_migrations_count
: Deployer migration counttwitter_reuses_count
: Twitter reuse count
Additional Fields
source
: Token source/factoryfactory
: Factory addresspoolAddress
: Associated pool addressdeployer
: Token deployer addresstokenSymbol
: Token symboltokenName
: Token namedexscreenerListed
: Whether listed on DexScreenerdexscreenerHeader
: DexScreener header statusdexscreenerAdPaid
: DexScreener ad paid status
Advanced Token Filtering
Volume-Based Analysis
Holdings Concentration Analysis
Enhanced Liquidity Analysis
Bonding Curve Analysis
Price Performance Tracking
Social Presence Filtering
Recent Token Discovery
Message Types
Token Update Messages
The token-based mode uses the same message types as pool-based mode but withTokenDataSchema
instead of PoolDataSchema
.
Init Message
Sent when a view is first created or when reconnecting:New Token Message
Sent when a new token is added to a view:Token Update Message
Sent when token data is updated:Token Remove Message
Sent when a token is removed from a view:Note: In token-based mode, the message types are updated to reflect token operations:
new-token
, update-token
, remove-token
. The data structure follows TokenDataSchema
instead of PoolDataSchema
. The tokenKey
in remove messages uses the format chainId|tokenAddress
.View Management
View management works the same as in Pool-Based mode:Pause Views
Unpause Views
Unsubscribe
Unsubscribe functionality is identical to Pool-Based mode. See the Pool-Based documentation for complete unsubscribe examples.Data Compression
Data compression works the same as in Pool-Based mode with gzip compression available for reduced bandwidth usage.Performance Considerations
Token View Limits
- Maximum 10 views per connection
- Maximum 100 tokens per view
- Maximum 1000 total tokens across all views
Bandwidth Optimization
- Use
pause
to reduce bandwidth when views are not needed - Filter aggressively to reduce data volume
- Consider using
limit
to restrict token count - Use organic metrics for cleaner data without bot activity