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

PairFilterConnection
PairFilterConnection
See PairFilterConnection

Arguments

filters
PairFilters
A set of filters to apply. See PairFilters
statsType
TokenPairStatisticsType
The type of statistics returned. Can be FILTERED or UNFILTERED. Default is UNFILTERED. See TokenPairStatisticsType
phrase
String
A phrase to search for. Can match a token or pair contract address or ID (address:networkId), or partially match a token name or symbol.
pairs
[String]
A list of pair or token contract addresses or IDs (address:networkId) to filter by.
matchTokens
PairFilterMatchTokens
A set of token contract addresses that make up a pair. Can be used in place of a pair contract address. See PairFilterMatchTokens
rankings
[PairRanking]
A list of ranking attributes to apply. See PairRanking
limit
Int
The maximum number of pairs to return.
offset
Int
Where in the list the server should start when returning items. Use count+offset from the previous query to request the next page of results.

Example

Test this query in the Explorer →
{
  filterPairs(
    filters: {network: 1399811149}
    phrase: "PUMP"
    limit: 10
  ) {
    results {
      buyCount12
      highPrice24
      liquidity
      lowPrice24
      marketCap
      price
      priceChange24
      volumeUSD24
      pair {
        token0Data {
          address
          name
          symbol
        }
        token1Data {
          address
          name
          symbol
        }
      }
    }
  }
}

Usage Guidelines

  • Response limit: 200 pairs per request
  • Use phrase parameter for searching by token name, symbol, or pair address
  • Apply quality filters such as volume and liquidity minimums to avoid low quality pairs
  • Results include pre-computed stats like priceChange24, volumeUSD24, buyCount12, etc. for easy display

Troubleshooting Tips

Use filterPairs when you want to discover or search trading pairs and need pair-specific data like which tokens are paired together. Use filterTokens when you want to discover tokens and need token-level aggregate data across all their pairs.
Each pair has token0Data and token1Data. One will be your target token, the other is typically a quote token (like USDC, WETH, or SOL). Check the address field to identify which is which, or filter by a known quote token address.
Add quality filters to improve results. Set minimum thresholds for liquidity and volumeUSD24 to filter out inactive or low-liquidity pairs.
Use the token0 or token1 filter with the token address, or use phrase to search by token name/symbol. You can also filter by network to narrow results to a specific chain.
Yes — use filterPairs for this. It accepts pool addresses via the phrase parameter or filters and returns metadata for many pairs in a single call.
Use filterPairs with a phrase containing the token’s address (formatted as address:networkId) and rank by liquidity descending:
filterPairs(
  phrase: "0x6982508145454ce325ddbe47a25d4ec3d2311933:1"
  rankings: { attribute: liquidity, direction: DESC }
)
The liquidity value represents the USD value of the base token (e.g. ETH or a stablecoin) backing the pair. Price change metrics across multiple timeframes are available on both filterPairs and filterTokens.
phrase matches pair addresses or the symbols/names of the tokens in the pair. As with filterTokens, avoid sorting by createdAt for phrase searches — use liquidity, volumeUSD24, or trendingScore24 for more meaningful rankings. See filterTokens — How does phrase search work? for the same gotcha at the token level.
  • Discover Tokens: Build token discovery pages with trending data, filters, and search