The Impact Hub Registry is a service that keeps reporting records for programmes: domains and projects, devices and households, claims and credits. Use this guide to decide which of your workflows go to the Registry API and which go to the IXO Protocol, so that one flow does not mix the two. The protocol's own transactions and gateways are documented in the API reference pages for the protocol interfaces.
Info
This is a design guide. It helps you plan, and it gives you nothing to run. The endpoints and their contracts are in the Registry API reference.
Before you start
- Confirm the active Registry endpoint in Networks and endpoints.
- Confirm what the Registry requires for authentication in the Authentication matrix.
- Confirm product and SDK names in the Product and SDK map.
Registry workflows
- Domain and project records
- Device and household reporting
- Claims and credit lifecycle reporting
- Health and operational checks
Service or protocol
| Use | For | Reference |
|---|---|---|
Registry API | Service workflows | Registry API |
| Protocol gateways | Direct chain queries and transactions | Blockchain RPC API and gRPC gateway API |
Check the result
A working integration shows:
- authenticated responses from the Registry service endpoints
- no chain RPC values guessed into service requests