Envio and The Graph endpoints
Joltzu plans to provide its own Envio HyperIndex and The Graph query endpoints for testnet and mainnet. All URLs are TBD. Service availability, indexed applications, schemas and access policies will be published with each deployment.
Planned Joltzu-hosted endpoints
| Service | Network | Query API | URL |
|---|---|---|---|
| Envio | Joltzu Testnet | HyperIndex GraphQL | TBD |
| The Graph | Joltzu Testnet | Subgraph GraphQL | TBD |
| Envio | Joltzu Mainnet | HyperIndex GraphQL | TBD |
| The Graph | Joltzu Mainnet | Subgraph GraphQL | TBD |
The same entries appear in the network directory. Local development uses an indexer you configure yourself.
Choose a query API
Envio HyperIndex turns application events into queryable entities served through GraphQL. Studio can export an Envio indexer with an application. See the public Envio HyperIndex guide.
The Graph serves GraphQL queries over entities defined by a deployed subgraph's schema. Each application/subgraph needs its published query URL; a network entry alone does not establish which data it indexes. See The Graph's query API.
Use these APIs to read indexed application data. Send transactions through JSON-RPC. An indexer can lag the chain, so confirm critical settlement against committed blocks or receipts.
Request template
Once an endpoint is published, set JOLTZU_INDEXER_URL to the query URL for the selected network and application:
curl "${JOLTZU_INDEXER_URL:?Set the published Envio or The Graph query URL}" \
-H 'Content-Type: application/json' \
--data '{"query":"query EndpointCheck { __typename }"}'
This minimal request checks GraphQL connectivity. For application data, use the published schema and its pagination/filter rules. Add the deployment's required authentication headers when applicable, and check GraphQL errors even when HTTP returns 200. No URL, credential or application schema is assumed by this template.
For operating your own indexer, see indexing blocks and events.