Use this page to understand auth surface area by API family. For canonical literals (headers, token sources, environment-specific behavior), use the authentication 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.
Scope
- This page summarizes auth methods by API surface.
- It does not define a single universal flow for all IXO APIs.
- Protocol docs and service docs can require different credentials.
Common request patterns
Common header formats used across IXO docs are centralized in/reference/authentication-matrix.
API families and auth responsibility
Protocol gateways
Protocol gateways
- Surfaces:
/api-reference/rpc-api,/api-reference/grpc-gateway-api - Auth notes: Chain and node access patterns vary by network and deployment.
Service APIs
Service APIs
- Surfaces:
/api-reference/blocksync-graphql-api,/api-reference/matrix-state-bot-api,/api-reference/registry-api - Auth notes: Service operators can enforce different credentials and scopes.
Security baseline
- Use HTTPS for all authenticated requests.
- Keep credentials in secure runtime storage, not source files.
- Rotate tokens and keys according to your operator policy.
- Log request identifiers and auth failures for incident triage.
Source-of-truth references
Authentication matrix
Use canonical auth literals and requirements by interface.
Networks and endpoints
Confirm network-specific endpoint mappings before integration.
Product and SDK map
Navigate IXO products, APIs, and SDK references.