Authentication
Use browser sessions in the workspace and scoped API keys in your own integrations.
Choose the right authentication method
Public read endpoints accept unauthenticated requests. The browser workspace uses a same-origin session cookie. Server-side order integrations use a workspace API key in the Authorization header.
| API surface | Authentication |
|---|---|
| Public inventory, catalogs, network, and analytics | No credentials required. |
| /api/resources | Member session or a resources-scoped API key. |
| /api/v1/dataset-orders | API key with orders:write. |
| Batch API: /api/openai/v1 and /api/v1/files | API key with orders:write. |
| /api/v1/evaluations | API key with evaluations:write. |
| /api/v1/training | API key with training:read or training:write; mutations need training:write. |
| /api/v1/balance | API key with orders:write, evaluations:write, training:read or training:write. |
| /api/batch (the Training Data page), datasets, training runs, account, and billing | Browser session; these corridors reject Authorization headers. |
Create a scoped key
Open API keys in your signed-in workspace. Choose a name and the smallest scope your integration needs. The token is displayed once when created; keep it server-side. An optional expiresAt is a future Unix-second timestamp no more than one year ahead; do not assume every key expires automatically. Revoke unused keys from the workspace.
Creating an orders:write, evaluations:write or training-scoped key requires approval for the corresponding task type. These scopes are separate. A dataset-order key cannot manage evaluations, training or saved configurations. Training keys use the dedicated /api/v1/training corridor; editing drafts requires a separate resources:write key.
| Scope | Purpose |
|---|---|
| resources:read | Read your saved workspace resources and owned CPU jobs. |
| resources:write | Manage saved drafts and approved CPU validation jobs; training and native operator execution retain their separate permissions. |
| orders:write | Quote, create, read, and cancel dataset orders; upload Batch API files and manage batches, including evaluations on your own file. |
| evaluations:write | Quote, create, read, and cancel evaluation orders on catalog sets. |
| training:read | Read training capabilities, owned runs, datasets, artifacts and balance. |
| training:write | Read training data, upload and manage datasets, quote, launch and cancel approved runs. |
Manage API keys — Create, inspect, or revoke keys in your workspace.
Make an authenticated read
Set RELIQUARY_API_KEY in your local or server environment using an order, evaluation or training key. This request reads your balance and recent ledger entries; it does not reserve credits.
Balance · scoped API key
: "${RELIQUARY_API_KEY:?Set your workspace API key}"
curl --fail-with-body --silent --show-error \
-H "Authorization: Bearer $RELIQUARY_API_KEY" \
'https://api.reliqua.ai/api/v1/balance'Browser session rules
The app sends same-origin session cookies and the X-XSRF-TOKEN header on mutations. Sign-in and wallet confirmations run through the native workspace flow. Use that flow for dataset-library uploads, training, Training Data orders in the app, account management, and billing. The Batch API (/api/openai/v1 and /api/v1/files) is not a browser corridor: it takes an orders:write API key.
A session_required response means the route expects the browser session. Remove the API-key integration from that path and use the documented /api/v1 route where one exists.