Sismo Docs
  • Welcome to Sismo
    • What is Sismo?
  • Build with Sismo Connect
    • Overview
    • Installation
    • Sismo Connect Cheatsheet
    • Tutorials
      • Get Your appId - Create a Sismo Connect App
      • Onchain Tutorial (1/2): Code Your Airdrop Contract With Privately-Aggregated Data
      • Onchain Tutorial (2/2): Deploy Your Airdrop Contract
    • Technical Documentation
      • Sismo Connect Configuration
      • Auths
      • Claims
      • Signature
      • Packages
        • Sismo Connect Client: Request
        • Sismo Connect React: Request
        • Sismo Connect Server: Verify Offchain
        • Sismo Connect Solidity Library: Verify Onchain
    • FAQ
  • Data Groups
    • Overview
    • Tutorials
      • Factory Guide: Create a Data Group in 5 Minutes
      • Sismo Hub Guide: Create Data Groups Programmatically
      • Sismo Hub Guide: Add a Data Provider to the Sismo Factory
    • Sismo Hub
      • Sismo Hub Repository
        • Group Generators
        • Data Providers
        • Data Operators
        • Command Line Interface
      • Accounts Registry Tree
  • Data Vault
    • Overview
    • Vault Identifiers
    • Proving Schemes
      • Hydra-S1
      • Hydra-S2
    • Commitment Mapper
  • Resources
    • Deployed Contract Addresses
    • Sismo API
      • API Links
      • Query From a Client
      • Group
        • Get groups
        • Get group snapshots
      • Common Parameters
      • Advanced Filtering
      • Transaction
  • Links
    • Sismo Landing Page
    • Sismo Factory
    • Sismo App Store
    • Sismo Builder Resources
    • GitHub
    • Discord
    • Twitter
    • Blog
Powered by GitBook
On this page
  1. Resources
  2. Sismo API

Advanced Filtering

Advanced usage of the API

PreviousCommon ParametersNextTransaction

Last updated 1 year ago

Before this, make sure you read the page about .

How to use where

The where filter lets you do some advanced queries. Here is how it works:

On String field

  • fieldname: "value"

  • fieldname_not: "value"

  • fieldname_in: ["value1", "value2"]

  • fieldname_not_in: ["value1", "value2"]

On Int , BigInt and DateTime field

  • fieldname: value

  • fieldname_not: value

  • fieldname_in: [value1, value2]

  • fieldname_not_in: [value1, value2]

  • fieldname_gt: value

  • fieldname_lt: value

On nested field

query {
    badges(
        where: {
            tokenId: 15151111,
            balance_gt: 1,
            attestation: {
              timestamp_gt: 1600000000
            }
        }
    ) {
        balance
        metadata {
            name
        }
        owner {
            id
        }
    }
}
common parameters