This endpoint is only available to Growth and Enterprise plans.
Endpoint details
- URL: wss://pulse-api.mobula.io
- Message format: JSON string
Basic Parameters
Easy Configuration
For basic usage, use thechainId
and poolTypes
parameters:
Available Parameters
-
chainId
(string | string[]): Blockchains to monitor- Available values example:
evm:6342
,evm:2741
,evm:80094
,evm:8453
,evm:56
,solana:solana
- Available values example:
-
poolTypes
(string | string[]): Pool types/factories to monitor- Launchpad pools:
pumpfun
,moonshot-sol
,liquidlaunch
,boop
,raydium-launchlab
,gte-bonding-v1
,mana
,fourmeme
,moonshot-evm
- Other pools:
uniswap-v2
,uniswap-v3
,raydium
,orca
,meteora
, etc.
- Launchpad pools:
-
personalizedId
(string, optional): Custom identifier for tracking client sessions- This ID will be included in all WebSocket responses for this connection
- Useful for tracking multiple clients or sessions
- Maximum length: 255 characters
Personalized ID Usage
ThepersonalizedId
parameter allows you to tag your WebSocket connection with a custom identifier. This identifier will be included in all responses from the server, making it easier to track and manage multiple connections or user sessions.
- Multi-user applications: Track which user a WebSocket message belongs to
- Session management: Identify different browser tabs or application instances
- Analytics: Correlate WebSocket data with user behavior or application state
- Debugging: Easily identify which client is receiving specific data
Default Model
Use thedefault
model to automatically get three views: new
, bonding
, and bonded
:
- new: Newly created tokens (sorted by
created_at
desc) - bonding: Tokens in bonding phase with activity (sorted by
market_cap
desc) - bonded: Bonded tokens on traditional DEXs (sorted by
created_at
desc)
Custom Views
For granular control, use theviews
parameter:
View Structure
Available View Models
Model “new”
Retrieves newly created tokens:Model “bonding”
Retrieves tokens in bonding phase with activity:Model “bonded”
Retrieves bonded tokens available on DEXs:Pattern Search in Views
Search for tokens by name or symbol directly in view configuration:View Parameters
Sorting and Pagination Parameters
-
sortBy
(string): Sort field- Options:
created_at
,market_cap
,volume_1h
,latest_trade_date
,price_change_1h
,price_change_24h
,trades_1h
,trades_24h
,liquidity
,holders_count
,buys_1h
,buys_24h
,sells_1h
,sells_24h
,buyers_1h
,buyers_24h
,sellers_1h
,sellers_24h
- Default:
created_at
- Options:
-
sortOrder
(string): Sort order- Options:
asc
,desc
- Default:
desc
- Options:
-
limit
(number): Number of results per view- Maximum: 100
- Default: 50
-
offset
(number): Offset for pagination- Default: 0
-
addressToExclude
(string | string[]): Addresses to exclude from results- Automatically excludes pools where the address appears as token0, token1, or pool address
- Can be a single address string or array of addresses
- Default: undefined
-
pattern
(string): Search pattern for token symbol or name (case insensitive)- Can be used directly in view configuration for quick filtering
- Alternative to using
pattern
in filters object - Default: undefined
Filters
Filters allow filtering on token properties based on thePoolsPriceChangeUSD
schema. All filters support multiple comparison operators.
For complete filter documentation including all available fields, operators, and examples, see Filter Details.
Filter Structure
The filter structure usesfilters
with optional nested pools
filters for pool-specific properties:
Quick Filter Examples
Price and Market Cap Filters
Volume and Activity Filters
Trading Activity Filters
Holdings Analysis Filters
Pattern Search and Social Media
Address Exclusion
TheaddressToExclude
parameter provides a simple way to exclude specific addresses from the results. This automatically filters out any pools where the specified address appears as:
- token0 (first token in the pool)
- token1 (second token in the pool)
- pool address (the pool contract address itself)
Address Exclusion Examples
Single Address Exclusion
Multiple Address Exclusion
Old Structure (Deprecated)
New Structure (Recommended)
Complete Examples
Example 1: All Available Filters
Example 2: High-Volume New Tokens with Factory Names
Example 3: Multi-Chain Bonded Analysis
Example 4: Address Exclusion with LiquidLaunch
Example 5: Pattern Search with Social Media Requirements
Example 6: Advanced Trading Activity Analysis
New Trading Activity Fields
The Pulse API now provides detailed trading activity metrics separated by transaction type and time periods:Trading Metrics Breakdown
- Trades: Total number of transactions (buys + sells)
- Buys: Number of buy transactions only
- Sells: Number of sell transactions only
- Buyers: Number of unique addresses that bought
- Sellers: Number of unique addresses that sold
Time Periods Available
All trading metrics are available for the following time periods:1min
- Last minute5min
- Last 5 minutes15min
- Last 15 minutes1h
- Last hour4h
- Last 4 hours6h
- Last 6 hours12h
- Last 12 hours24h
- Last 24 hours
Metadata Fields
tokenSymbol
: The token’s symbol (e.g., “BTC”, “ETH”, “DOGE”)tokenName
: The token’s full name (e.g., “Bitcoin”, “Ethereum”, “Dogecoin”)dexscreenerListed
: Boolean indicating if the token is listed on DexScreener
Use Cases
These fields enable more sophisticated filtering and analysis:Available Pool Types
Launchpad Pools
pumpfun
- Pump.fun (Solana)moonshot-sol
- Moonshot (Solana)moonshot-evm
- Moonshot (EVM)fourmeme
- 4meme (EVM)liquidlaunch
- LiquidLaunch (EVM)boop
- Boop (Solana)raydium-launchlab
- Raydium Launchlab (Solana)gte-bonding-v1
- GTE Bonding V1 (EVM)mana
- Mana (EVM)meteora-dbc
- Meteora Dynamic Bonding Curve (Solana)
DEX Pools
uniswap-v2
- Uniswap V2 (EVM)uniswap-v3
- Uniswap V3 (EVM)raydium
- Raydium AMM (Solana)raydium-clmm
- Raydium CLMM (Solana)raydium-cpmm
- Raydium CPMM (Solana)orca
- Orca (Solana)meteora
- Meteora (Solana)meteora-dyn
- Meteora Dynamic (Solana)meteora-dyn2
- Meteora Dynamic V2 (Solana)algebra
- Algebra (EVM)camelot-v2
- Camelot V2 (EVM)curve
- Curve (EVM)balancer
- Balancer (EVM)iziswap
- iZiSwap (EVM)solidly-v3
- Solidly V3 (EVM)lbv2.1
- Liquidity Book V2.1 (EVM)
Response Format
The stream returns objects with the following structure:Key Differences from V1
The V1 response format includes all the new fields from the updatedPoolDataSchema
:
- Enhanced Price Data: Additional time periods (1min, 15min, 6h, 12h)
- Trading Activity: Detailed breakdown of buys, sells, buyers, sellers, and traders
- Fees Analysis: Fees paid across all time periods
- Holdings Analysis: Comprehensive holdings breakdown including dev, insider, sniper percentages
- Metadata: Enhanced token information with symbol, name, and DexScreener listing status
Pause/Unpause Views
You can pause and unpause specific views without disconnecting from the stream:Pause Views
To pause specific views, send:Unpause Views
To unpause specific views, send:Pause/Unpause Parameters
-
action
(string): Action to performpause
: Pause the specified viewsunpause
: Resume the specified views
-
views
(string[]): Array of view names to pause/unpause- Must match the view names from your original subscription
Pause/Unpause Examples
Pause All Default Views
Pause Custom Views
Unpause Specific Views
Pausing views reduces bandwidth usage and processing load while maintaining your connection. You can pause/unpause views at any time without needing to resubscribe.
Unsubscribe from Stream
To unsubscribe, send:Use the Network tab in your browser to see WSS requests in real time.