> ## 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.

# Description

> Developer credentials, organizations, and identity for the Fluide Suite.

The **Auth API** covers developer session management and identity for Fluide Connect integrations.

## Token exchange (start here)

Server integrations obtain a machine JWT from **`POST /api/v1/authorize/token`** using `X-Fluide-Api-Key`, `X-Fluide-Api-Secret`, and `X-Fluide-Client-Id: fluide-developer`. This route does **not** use a Bearer token.

<Card title="POST /authorize/token" icon="key" href="/api-reference/auth/exchange-api-key-for-access-token">
  Open in API reference with playground
</Card>

See also [Authorization](/getting-started/authorization) for curl and Node.js walkthroughs.

## Base path

`/api/v1`

## Authorization

| Context                     | Headers                                                                                     |
| --------------------------- | ------------------------------------------------------------------------------------------- |
| Developer session endpoints | `Authorization: Bearer <token>`, `X-Fluide-Api-Key`, `X-Fluide-Client-Id: fluide-developer` |

See [Authorization](/getting-started/authorization) for curl and Node.js examples.

### API playground

For **Developer Access** endpoints (`current`, `rotate-secret`), click **Authorize** and set **Bearer**, **X-Fluide-Api-Key**, and **X-Fluide-Client-Id** (`fluide-developer`).

## Operations and monitoring

| Endpoint             | Purpose                                              |
| -------------------- | ---------------------------------------------------- |
| `GET /api/v1`        | Service root — quick connectivity check              |
| `GET /api/v1/health` | Health check with dependency status (database, etc.) |

<Note>
  Prometheus metrics for auth may be exposed on the service directly depending on deployment. Check the **Operations** tag group in the sidebar for `App` and `Health` endpoints.
</Note>

## What to build first

<Steps>
  <Step title="Call a product API">
    Use your access token on HR, Payroll, Pay, Books, or Utils routes.
  </Step>

  <Step title="Rotate if needed">
    Use `POST /api/v1/authorize/rotate-secret` or the Connect dashboard if a secret is exposed.
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Product guide" icon="book" href="/auth/overview">
    Developer credentials and credential lifecycle.
  </Card>

  <Card title="How-to guides" icon="book-open" href="/guides/service-partner/onboard-client-company">
    Partner onboarding, workspaces, KYB, and acting-client headers.
  </Card>
</CardGroup>