This endpoint requires a Growth or Enterprise plan. Learn more.
Returns
[LaunchpadTokenEventOutput!]!
Arguments
OnLaunchpadTokenEventBatchInput
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
Test this query in the Explorer →Example Response
Usage Guidelines
- This subscription is scoped to the launch lifecycle: events stream from token creation through the bonding curve, then for 6 hours post-migration (graduation). After that window, tokens age out of the stream — for continued coverage, hand off to the standard subscriptions (see below)
- 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.Why do events stop 6 hours after a token migrates?
Why do events stop 6 hours after a token migrates?
The 6-hour window is by design. This subscription covers the launch lifecycle — creation, bonding curve progress, and graduation/migration. Once a token migrates there are no further launchpad lifecycle events for it, and keeping every graduated token in this high-volume stream would only duplicate data available from the standard subscriptions. In practice, most launchpad tokens see their activity die off within a few hours of migration, so 6 hours captures the volatile post-graduation period for nearly every token.For tokens that keep trading past that window, switch to the standard subscriptions: when you receive a
Migrated event, subscribe to the token with onTokenEventsCreated or onPriceUpdated for continuous coverage with no gap.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.Created events have a 3-4s delay. Is there a faster way to see newly launched tokens?
Created events have a 3-4s delay. Is there a faster way to see newly launched tokens?
Use
eventType: Deployed instead for faster updates. The two events are:Deployed— sent immediately when the token contract is discovered (minimal latency). Includes fundamentals but may lack metadata like images.Created— sent after metadata is fetched (3-4s latency). Includes complete token information.
Deployed for immediate notification and Created to fill in metadata when it arrives. We have plans to reduce Created latency further (especially on Solana) while keeping the same Deployed → Created flow.Related Recipes
- Launchpads: Build a launchpad discovery view with real-time token lifecycle updates
- Launchpad Lifecycle: Understand how tokens progress through launchpad stages from bonding curve to graduation