📗
HyperGraph English
  • Welcome to HyperGraph
  • 💰 Farming
    • Introduction of Minning
      • Connecting MetaMask to Binance Smart Chain
      • MathWallet on Binance Smart Chain APP Guide
      • Token Pocket App on Binance Smart Chain (BSC)
  • 🛠️ PRODUCT
  • Product usage
    • Product business
    • Registration and login
    • Create subgraph
    • View subgraph
  • Development
    • Business interaction process
    • Quick start
    • Remote deployment
    • Development and deployment FAQ
    • Subgraph development
    • GraphQL API
    • AssemblyScript API Part 1
    • AssemblyScript API Part 2
  • Example
    • Uniswap subgraph example
    • Uniswap-info example
  • User Cases
  • Public subgraph
  • 🪜HYPERBRIDGE
    • HyperBridge
    • Token cross-chain
    • Mainstream assets cross-chain
    • Mainstream assets liquidity provision
    • Cross-chain purchase of Gas
  • 📖 Project
    • Operation Flow
    • Index Nodes
    • Token Allocation
    • Contract Address
  • 🧩 Network
    • HyperGraph Introduction
    • Network Construction
    • Network Role
    • Node Device
    • Node Hosting Type
    • Pricing Plan Second Edition
    • Node Network FAQ
    • Heco archive node for public use
  • 🔗 Links
    • HyperGraph Site
    • HyperGraph Farming
    • BSC Explorer
    • 中文文档
Powered by GitBook
On this page

Was this helpful?

  1. Product usage

View subgraph

PreviousCreate subgraphNextDevelopment

Last updated 4 years ago

Was this helpful?

Enter the subgraph list page, the default is the list of all subgraph

You can also filter by public chain and click on the title or logo to enter the corresponding subgraph details page

Before deployment, we saw some simple basic information:

After the deployment and synchronization are completed, you can find the status of subgraph on the first page of the list is available:

In the details page, there are more subgraph information:

Here is a brief description of these items

Subgraph name: This is a name for internal deployment, which can be used for queries such as health status

AuthToken: It is useful when deploying in API mode. Use this Token to locate your subgraph and perform authorization operations, so as to ensure that only users with this AuthToken can modify the subgraph and redeploy

Subgraph code link: Refers to the uploaded code, which can be downloaded

Subgraph tag: This is the unique number of the subgraph in the system. If the code is changed, this number will change. If the code does not change, multiple deployments will not cause this number to change. If it is deployed by API, the code is updated, this number No change, please contact technical support.

HTTPS query API: The project can call this API in the product to query data, using GraphQL language to query, this link can also be opened in the browser to enter the playground (Playground)

WebSocket query API: the function is the same as HTTPS query API, but it supports WebSocket connection

Test bench: Users can use this link for some query and debugging

Master contract: This is separated from subgraph.yaml, this subgraph is the main analysis contract

Health status: This is the global health status URL, you can use the sub-picture name to check the synchronization of this sub-picture

At the same time, the log can also be viewed:

The log can also be filtered by classification, which will not be described in detail here. The statistical function will be developed and improved in the future, so stay tuned.