Skip to main content
IXO Blocksync is an indexing and query service. It is not the canonical protocol transaction interface.

​
Overview

  • Use this API for indexed, flexible querying.
  • Treat this as a service layer over chain data.
  • Use protocol gateways for direct protocol operations.

​
Service boundary

  • In scope: GraphQL query patterns, filters, and pagination.
  • Out of scope: transaction submission and module-level protocol semantics.

​
Example queries

query {
  entities(first: 10) {
    edges {
      node {
        id
        name
        type
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}

query {
  entities(
    filter: {
      type: { equalTo: "ORGANIZATION" }
      status: { equalTo: "ACTIVE" }
    }
  ) {
    edges {
      node {
        id
        name
        status
      }
    }
  }
}

​
Authentication and endpoints

Authentication matrix

Verify required credentials and auth patterns by interface.

Networks and endpoints

Confirm endpoint mappings by network and environment.

​
Troubleshooting

  • 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 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 via RPC/REST if you need authoritative height.
  • Introspection disabled — Some deployments turn off schema introspection in production; use a saved schema or dev environment for tooling.

Pagination

Apply consistent pagination patterns across API queries.

Blockchain RPC API

Use RPC endpoints for direct blockchain node interactions.

Product and SDK map

Navigate IXO products, APIs, and SDK references.