This endpoint requires a Growth or Enterprise plan. Learn more.
Returns
AddEventsByMakerOutput
Arguments
OnEventsCreatedByMakerInput!
required
[EventCommitmentLevel!]
The commitment levels to subscribe to. When multiple commitment levels are subscribed to, events are emitted at most once per increasing commitment stage per subscriber. If a stronger commitment level is observed first, later weaker updates for the same event are suppressed for a short in-memory window. Preprocessed is supported only for Solana event subscriptions. Preprocessed evaluates pre-execution events and can differ significantly from processed or confirmed output. In particular, preprocessed swaps may use aggregator swaps before it is known how execution will route the underlying swaps, and many preprocessed events may error and never be processed.
See EventCommitmentLevel
Example
Test this query in the Explorer →Example Response
Usage Guidelines
- Subscribe with
makerAddressto stream all transactions made by a specific wallet in real-time - Events are streamed across all pairs and tokens — not scoped to a single pair or network
- Each event includes the
address(pair address) andnetworkIdso you can identify which pair/network the trade occurred on - The
Eventtype is the same as returned byonEventsCreated, including swap values, wallet metadata, and sandwich detection labels - Use this to build wallet-following features, copy-trading bots, or real-time alerts for specific traders
Troubleshooting Tips
How does this differ from onEventsCreated?
How does this differ from onEventsCreated?
onEventsCreated streams events for a specific pair or all pairs on a network. onEventsCreatedByMaker streams events for a specific wallet across all pairs and networks. Use this when you want to follow a trader’s activity regardless of which tokens they’re trading.Can I filter by network or token?
Can I filter by network or token?
No. This subscription streams all events for the wallet across all networks and pairs. Filter client-side if you only want events for specific tokens or networks using the
networkId and token0Address/token1Address fields.What event types are included?
What event types are included?
All event types are included:
Swap, Mint, Burn, Sync, Collect, CollectProtocol. Most wallet-tracking use cases focus on Swap events — filter by eventType or eventDisplayType (Buy/Sell) as needed.Is there rate limiting or volume concerns?
Is there rate limiting or volume concerns?
High-activity wallets (like market makers or bots) may produce many events per second. Consider whether you need all events or can sample/filter client-side. For very high-volume wallets, you may want to batch or throttle your processing.
Related Recipes
- Events: Build a token swap list with filtering, pagination, and real-time updates