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

# API reference

> Browse and try Fluide API endpoints in Connect.

# API reference

Each product has an **overview page** with context, monitoring endpoints, and integration flows — then generated endpoint pages from OpenAPI below it in the sidebar.

| Product | Overview                              | Base path          |
| ------- | ------------------------------------- | ------------------ |
| Auth    | [Auth API](/api-reference/auth)       | `/api/v1`          |
| HR      | [HR API](/api-reference/hr)           | `/api/v1/hr`       |
| Payroll | [Payroll API](/api-reference/payroll) | `/api/v1/payroll`  |
| Pay     | [Pay API](/api-reference/pay)         | `/api/v1/payments` |
| Books   | [Books API](/api-reference/books)     | `/api/v1`          |
| Utils   | [Utils API](/api-reference/utils)     | `/api/v1/app`      |

Open any endpoint to see parameters, request bodies, responses, and try the **interactive playground** with **cURL** and **Node.js** examples.

## Playground authorization

The playground prompts for three credentials on every product route (including health checks):

| Header               | Playground field       | Required value                  |
| -------------------- | ---------------------- | ------------------------------- |
| `Authorization`      | **Bearer**             | Your access token JWT           |
| `X-Fluide-Api-Key`   | **X-Fluide-Api-Key**   | Your `fl_dev_...` developer key |
| `X-Fluide-Client-Id` | **X-Fluide-Client-Id** | `fluide-developer`              |

Click **Authorize** before **Send**. If you skip it, the API returns `400 Authorization field missing` or `401` with codes such as `MISSING_API_KEY` or `CLIENT_AUDIENCE_MISMATCH`.

<Card title="Get credentials" icon="key" href="/getting-started/authorization">
  Header reference and step-by-step playground setup.
</Card>

## Operations endpoints

Every service exposes operational routes under the **Operations** tag group where applicable:

* **App** — service root (`GET`)
* **Health** — liveness and dependency checks
* **Prometheus** — metrics scrape target (`/metrics` or product-prefixed path)

## Keep specs up to date

```bash theme={null}
node export-openapi.mjs
```