Subscriptions (WebSockets) require a Growth or Enterprise plan. Learn more.
For monitoring pool graduations, use
Migrated events instead of Completed events. While both event types are currently saved to our database, only Migrated events are actively emitted via subscriptions. The Completed event is a legacy state and will be deprecated in a future release.Example Response
Usage Guidelines
- Filter by
protocol(e.g.,Pump,Clanker,Virtuals) orlaunchpadNamefor more specific filtering - Use
eventTypeto subscribe to specific lifecycle events:Created,Updated,Migrated - Events are batched for efficiency - each message may contain multiple token events
- Use
networkIdto filter by specific chain (e.g., 1399811149 for Solana, 8453 for Base) - Monitor
sniperCount,bundlerCount, andinsiderCountto assess token quality - Use
devHeldPercentageto check developer token holdings
Troubleshooting Tips
What's the difference between eventType options?
What's the difference between eventType options?
Deployed: Token contract discovered on-chainCreated: Token has metadata populatedUpdated: Token stats updated (price, volume, holders)Migrated: Token graduated from bonding curve to DEXUnconfirmedDeployed/UnconfirmedMetadata: Early events before finalization
Why use this instead of onLaunchpadTokenEvent?
Why use this instead of onLaunchpadTokenEvent?
onLaunchpadTokenEventBatch batches multiple events per message, reducing WebSocket overhead. Use this for high-throughput applications monitoring many tokens.How do I monitor token graduations?
How do I monitor token graduations?
Subscribe to
eventType: Migrated to receive events when tokens graduate from bonding curves to DEX pools. This is the recommended approach over Completed events.What do sniperCount and bundlerCount indicate?
What do sniperCount and bundlerCount indicate?
sniperCount is wallets that bought very early (potential bots). bundlerCount is wallets that bundled transactions. High values may indicate coordinated buying or manipulation.