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

Sismo API

GraphQL API for Sismo

PreviousDeployed Contract AddressesNextAPI Links

Last updated 1 year ago

You found the Sismo API documentation! Here, we aim to outline all of Sismo’s public API endpoints and explain how to use them.

The Sismo protocol makes use of data from both onchain and offchain sources. The Sismo API allows developers to fetch the data they need from either source. As the API is GraphQL-based, developers only fetch the data they request—with no unnecessary information.

The goal of the Sismo API is to aggregate the onchain & offchain information into two GraphQL endpoints—one for production networks (Ethereum, Polygon, & Gnosis) and the other for testnets (Goerli & Mumbai). Making these endpoints public makes it extremely easy for developers to build with Sismo—pathing the way for mass adoption.

We plan to continuously update this API and pack it with as many features as possible. Any feedback is greatly appreciated. We hope you enjoy using it!

Need help or have feedback? Check out #api-support on our !

Discord