Executions and Results
Filtering
Our API supports filtering on all /results
endpoints to refine query results. You can apply filters on both rows and columns to narrow down the data returned by the API. This feature is available for the following endpoints:
Filtering can be effectively used in conjunction with pagination and sorting to further enhance query efficiency and relevance. See an example of filtering in action with this Dune farcaster frame.
Example Filtering Request
Filtering Parameters
filters
- Type:
string
- Description: Allows specifying criteria to filter rows in the result set. It functions similarly to a SQL
WHERE
clause. If omitted, all results are returned.
- Use the format
<column_name> <operator> <value>
for criteria, for example,block_time >= '2024-03-05 15:03'
. - Combine criteria using parentheses and logical operators
AND
/OR
, e.g.,block_time >= '2024-03-05 15:03' AND (project = 'uniswap' OR project = 'balancer')
. - The
IN
operator is permitted, as intx_to IN (0x6a3e4b7e23661108aaec70266c468e6c679ae022, 0xdbf89389504e39f03fbb6bdd601aabb6bfbbed71)
. - The
NOT
operator is not supported; usingNOT IN
orNOT LIKE
will produce an error. - For column names with special characters (e.g., spaces, emojis, dashes, dots), enclose them in double quotes:
"special, column" = 'ABC'
. - Values must be strings or numbers. SQL expressions like
now() - interval '1' day
are not allowed. - Dates and times should be formatted as strings, e.g.,
block_time > '2023-01-03'
.
columns
- Type:
string
- Description: Specifies the column names to include in the result set. If omitted, all columns are returned.
- List column names without spaces, e.g., use
project,block_time,amount_usd
instead ofproject, block_time, amount_usd
. - Specifying columns helps limit the results to essential data, reducing the data cost of the call.
Filtered Response
Was this page helpful?