> ## Documentation Index
> Fetch the complete documentation index at: https://ixoworld-mintlify-9a7944b6.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Registry API

> Application service API reference for Impact Hub Registry workflows.

This page covers the Impact Hub Registry service API. It is not a direct IXO Protocol gateway and should be treated as an application/service surface.

## Overview

* Service scope includes registry-facing workflows such as project, household, device, credit, and claim reporting interfaces.
* Protocol-level claim semantics and module transactions belong to IXO Protocol API pages.

## Authentication

Registry deployments can use service-specific credentials. The historical examples for this surface include HTTP Basic auth.

```http theme={null}
Authorization: Basic <base64(username:password)>
```

<Warning>
  Do not assume one auth scheme across all registry environments. Confirm active requirements in `/reference/authentication-matrix`.
</Warning>

## Endpoint groups

* System health and API docs
* Household and device reporting
* Fuel and claims reporting
* Credit lifecycle reporting

## Known literal handling

Historical environment literals for this surface have appeared in previous docs. This page no longer treats those values as canonical source of truth.

<CardGroup cols={2}>
  <Card title="Canonical endpoints" href="/reference/networks-and-endpoints">
    Use network and environment endpoint mappings as source of truth.
  </Card>

  <Card title="Canonical auth requirements" href="/reference/authentication-matrix">
    Confirm active authentication requirements before integration.
  </Card>
</CardGroup>

## Troubleshooting

* **`401 Unauthorized` with Basic auth** — Wrong username/password or environment rotated credentials; re-read the deployment row in [Authentication matrix](/reference/authentication-matrix).
* **`403 Forbidden`** — Authenticated but missing role or scope for that registry route; check operator RBAC and which program the credentials belong to.
* **`404` on resource paths** — Registry API versions and path prefixes differ by deployment; confirm OpenAPI/base URL with your operator ([Networks and endpoints](/reference/networks-and-endpoints)).
* **Payload validation errors** — Compare field names to the operator’s schema; many issues are missing required reporting fields, not transport failures ([Error handling](/api-reference/errors)).

## Related references

<CardGroup cols={3}>
  <Card title="Registry guide" href="/guides/registry">
    Follow task-oriented guidance for registry workflows.
  </Card>

  <Card title="API authentication" href="/api-reference/authentication">
    Review authentication patterns used across IXO API interfaces.
  </Card>

  <Card title="Product and SDK map" href="/reference/product-and-sdk-map">
    Navigate IXO products, APIs, and SDK references.
  </Card>
</CardGroup>