Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.codex.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Returns

​
MakerEventConnection
MakerEventConnection
See MakerEventConnection

​
Arguments

​
limit
Int
The maximum number of events to return.
​
query
MakerEventsQueryInput!
required
The query filters to apply to the results. See MakerEventsQueryInput
​
cursor
String
The cursor to use for pagination.
​
direction
RankingDirection
The order to receive the token events. Can be DESC (default) or ASC. See RankingDirection

​
Example

Test this query in the Explorer → 
{
  getTokenEventsForMaker(
    query: {maker: "71CPXu3TvH3iUKaY1bNkAAow24k6tjH473SsKprQBABC", eventType: Swap}
    direction: DESC
    limit: 10
  ) {
    items {
      address
      baseTokenPrice
      eventDisplayType
      timestamp
      token0Address
      token0ValueBase
      token1Address
      token1ValueBase
      eventType
      data {
        ... on SwapEventData {
          amount0
          amount1
          priceBaseToken
          priceBaseTokenTotal
          priceUsd
          priceUsdTotal
        }
      }
      transactionHash
    }
    cursor
  }
}

​
Usage Guidelines

  • Specify a desired eventType (eg: Swap, Mint, Burn, etc.) to suit your needs on any supported network and timeframe
  • Narrow results by specific network, token address, and combine with filters such as priceUsdTotal for more targeted results.
  • Note: Token transfer events are not supported
  • Multi-hop transactions will show each intermediate transaction separately (see troubleshooting tip below for details)

​
Troubleshooting Tips

Yes this is expected behavior for a multi-hop transaction, where a maker will initiate a transaction from Token A -> Token B -> Token C, for example. We understand that Token B is likely of zero interest, however, it is still a legitimate transaction that we must index. Using the transaction hash to disambiguate on the client side is really the only way to attempt to simplify the swap down to just Token A -> Token C.
The transaction most likely occured on a protocol that we do not support. While we endeavor to support as many dexes as possible, including thousands of Uniswap forks, there are some we may not have yet. You can reach out to our team to inquire about specific exchanges you would like to see supported in a future update.
Look at the signs of amount0 and amount1 in the data field:
Negative amount = Token received (bought)
Positive amount = Token spent (sold)This rule is consistent for ALL transactions:
Positive = what they gave up (OUT of wallet)
Negative = what they received (INTO wallet)The eventDisplayType “Buy”/“Sell” indicates the primary action from the user’s perspective (buying or selling the non-native token), while the amount signs show the actual token flows.
  • Events: Build a token swap list with filtering, pagination, and real-time updates
  • Wallets: Analyze wallet performance, discover top traders, and build portfolio views