Skip to main content
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.

POST /authorize/token

Open in API reference with playground
See also Authorization for curl and Node.js walkthroughs.

​
Base path

/api/v1

​
Authorization

See 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

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.

​
What to build first

1

Call a product API

Use your access token on HR, Payroll, Pay, Books, or Utils routes.
2

Rotate if needed

Use POST /api/v1/authorize/rotate-secret or the Connect dashboard if a secret is exposed.

Product guide

Developer credentials and credential lifecycle.

How-to guides

Partner onboarding, workspaces, KYB, and acting-client headers.