Skip to main content
This guide is for the Impact Hub Registry service layer. IXO Protocol module transactions and chain gateway behavior are documented in API reference pages for protocol interfaces.

​
Before you start

  • Confirm active Registry endpoint in /reference/networks-and-endpoints.
  • Confirm Registry auth requirements in /reference/authentication-matrix.
  • Confirm product and SDK naming in /reference/product-and-sdk-map.

​
What this guide does

You will map a registry workflow to the correct service endpoint group and verify service-level access without mixing protocol gateway calls into the same flow.

​
Core registry workflows

  • Domain and project records
  • Device and household reporting
  • Claims and credit lifecycle reporting
  • Health and operational checks

​
Service vs protocol boundary

  • Use Registry API for service workflows: /api-reference/registry-api
  • Use protocol gateways for direct chain queries and transactions:
    • /api-reference/rpc-api
    • /api-reference/grpc-gateway-api

​
Verify the result

A successful integration should show:
  • authenticated responses from Registry service endpoints;
  • no reliance on guessed chain RPC literals in service requests.

​
Next steps

  • Registry API reference: /api-reference/registry-api
  • Claims guide: /guides/dev/ixo-claims
  • Networks and endpoints: /reference/networks-and-endpoints