> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pruva.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Status and support

> Check that the API is up, and how to get help.

## Checking the API is up

The API exposes an unauthenticated health endpoint you can call or monitor at any time:

```bash theme={null}
curl https://api.pruva.africa/v1/health
```

A healthy response is:

```json theme={null}
{
  "status": true,
  "data": { "service": "pruva-api", "status": "ok" }
}
```

Point your uptime monitor at this endpoint. Because it needs no API key, you can monitor it without embedding a credential. See [Health check](/api-reference/health).

<Note>
  Health confirms the API itself is reachable. It does not test a specific scope's provider, so a healthy API can still return a `failed` check if an upstream provider is down. Watch your `failed` rate as well as the health endpoint.
</Note>

## Getting help

When you contact support, include the details that let us find the exact check:

<Steps>
  <Step title="The reference">
    The `reference` of the affected verification. This is the single most useful thing you can provide; it identifies the check precisely.
  </Step>

  <Step title="The environment">
    Whether it was `test` or `live`. The key prefix tells you.
  </Step>

  <Step title="What you expected and what you got">
    The `status` and any `errorMessage` you received, and what you expected instead.
  </Step>

  <Step title="When it happened">
    The approximate time, so we can line it up with logs.
  </Step>
</Steps>

<Warning>
  Never share your API key, or a webhook signing secret, in a support message. We never need your secret to help you. Share the `reference`, the status, and the error message instead.
</Warning>

## Before you reach out

Many issues resolve from the docs faster than a support round trip:

* A `403` is almost always approval or scope activation. See [Scopes and activation](/concepts/scopes-and-activation).
* A `402` is wallet balance. See [Wallet and billing](/concepts/billing).
* A `422` is the request body. See [Errors](/api-reference/errors).
* A check that "fails for everyone" on one scope is usually a configuration issue on that scope, worth checking in the dashboard first.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.