The IXO Blocksync GraphQL API is a read-only query interface over indexed IXO chain data. Use it when you need flexible queries, with filters and paging, that would be slow or awkward against a node.
IXO Blocksync is an indexing and query service, a layer over chain data. It is not the canonical protocol transaction interface: to submit transactions or read state at an exact height, use the protocol gateways.
Scope
| In scope | GraphQL query patterns, filters, and pagination |
| Out of scope | Transaction submission and module-level protocol semantics |
Example queries
A page of records with paging information. Pagination explains the cursor arguments.
query {
entities(first: 10) {
edges {
node {
id
name
type
}
}
pageInfo {
hasNextPage
endCursor
}
}
}A filtered query:
query {
entities(
filter: {
type: { equalTo: "ORGANIZATION" }
status: { equalTo: "ACTIVE" }
}
) {
edges {
node {
id
name
status
}
}
}
}Authentication and endpoints
| What you need | Where to find it |
|---|---|
| Required credentials and auth patterns | Authentication matrix |
| GraphQL endpoint for each network | Networks and endpoints |
Troubleshooting
| Problem | Cause and fix |
|---|---|
GraphQL errors with partial data | Treat the operation as failed if any required selection set is null. Fix variables and filters, then retry. Log extensions when present for server hints. |
| Auth failures | Service credentials differ by operator. Confirm against the Authentication matrix. Do not reuse protocol wallet keys as GraphQL API keys. |
| Stale or missing entities | Indexers lag behind chain head. Wait for sync, or query the same entity through RPC or REST if you need authoritative height. |
| Introspection disabled | Some deployments turn off schema introspection in production. Use a saved schema or a dev environment for tooling. |