This page documents the RPC interface family for IXO Protocol. It does not document application service APIs such as Impact Hub Registry, IXO Blocksync, or IXO Matrix.Documentation Index
Fetch the complete documentation index at: https://docs.ixo.world/llms.txt
Use this file to discover all available pages before exploring further.
Overview
- Use this interface for protocol-level operations against chain nodes.
- Prefer this when you need direct interaction with IXO Protocol modules.
- For indexed or application-service workflows, use service APIs in this section instead.
Protocol boundary
- In scope: chain state queries and transaction submission patterns.
- Out of scope: service-specific business endpoints and off-chain workflow APIs.
Authentication and endpoints
Authentication depends on node and deployment policy.- Check
/reference/authentication-matrixfor active auth requirements. - Check
/reference/networks-and-endpointsfor network-specific RPC endpoints.
Example message shapes
Troubleshooting
connection refused/ TLS errors — Wrong host, port, or TLS termination. Confirm the literal in Networks and endpoints and your operator’s current RPC URL.invalid JSON-RPC/ parse errors — Request body not valid JSON-RPC 2.0; includejsonrpc,id,method, andparamsas required by the method.- Transaction broadcast failures — Inspect
code,codespace, andrawLog. Common causes: insufficient fees, wrongchain-id, sequence mismatch, or missing signer permissions. See Error handling and Claims management. - Auth on RPC — Many nodes allow unauthenticated read; writes require a valid signed tx, not an API key. Confirm policy in Authentication matrix.
Related references
Blockchain REST API
Access protocol queries over HTTP/JSON through the gRPC gateway.
IXO Blocksync GraphQL API
Query indexed chain data through the IXO Blocksync service layer.
Product and SDK map
Navigate IXO products, APIs, and SDK references.