Skip to main content
This endpoint requires a Growth or Enterprise plan. Learn more.

Returns

[LaunchpadTokenEventOutput!]!
See LaunchpadTokenEventOutput

Arguments

OnLaunchpadTokenEventBatchInput
See OnLaunchpadTokenEventBatchInput
Launchpad events are extremely high-frequency and will send a large number of requests. We offer a monthly flat-rate option with unlimited requests for this subscription. Contact us for more information.
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.
You can find a complete list of supported launchpad protocols here, and a list of filterable launchpad names here. For more information on our Launchpad event subscriptions, see our Launchpads recipe page.

Example

Test this query in the Explorer →
Example Response

Usage Guidelines

  • Filter by protocol (e.g., Pump, Clanker, Virtuals) or launchpadName for more specific filtering
  • Use eventType to subscribe to specific lifecycle events: Created, Updated, Migrated
  • Events are batched for efficiency - each message may contain multiple token events
  • Use networkId to filter by specific chain (e.g., 1399811149 for Solana, 8453 for Base)
  • Monitor sniperCount, bundlerCount, and insiderCount to assess token quality
  • Use devHeldPercentage to check developer token holdings

Troubleshooting Tips

  • Deployed: Token contract discovered on-chain
  • Created: Token has metadata populated
  • Updated: Token stats updated (price, volume, holders)
  • Migrated: Token graduated from bonding curve to DEX
  • UnconfirmedDeployed/UnconfirmedMetadata: Early events before finalization
onLaunchpadTokenEventBatch batches multiple events per message, reducing WebSocket overhead. Use this for high-throughput applications monitoring many tokens.
Subscribe to eventType: Migrated to receive events when tokens graduate from bonding curves to DEX pools. This is the recommended approach over Completed events.
sniperCount is wallets that bought very early (potential bots). bundlerCount is wallets that bundled transactions. High values may indicate coordinated buying or manipulation.
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.
For the fastest results, subscribe to both and resolve the models on the frontend: use 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 DeployedCreated flow.
  • 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