All requests to the Oasis Liquido API must be authenticated using JSON Web Tokens (JWT). After a successful login or registration, the API returns anDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/FlasheyEstudi/Oasis-Liquido/llms.txt
Use this file to discover all available pages before exploring further.
access_token that you include in every subsequent request. A refresh_token is also issued to obtain a new access token when the current one expires, without requiring the user to log in again.
Base URL
The development base URL is:Authorization header
Pass your access token in theAuthorization header using the Bearer scheme:
Minimal curl example
Auth endpoint summary
| Method | Path | Description |
|---|---|---|
POST | /auth/register | Create a new user account |
POST | /auth/login | Authenticate and receive tokens |
POST | /auth/refresh | Exchange a refresh token for a new access token |
POST | /auth/logout | Invalidate the current session |
GET | /auth/me | Return the authenticated user’s profile |
Common error responses
| Status | Meaning | When it occurs |
|---|---|---|
401 Unauthorized | Missing or invalid token | No Authorization header, or the token is expired or malformed |
403 Forbidden | Insufficient role | The authenticated user’s role is not permitted for this endpoint |
409 Conflict | Resource already exists | Attempting to register an email address that is already in use |
The
refresh_token is set automatically as an httpOnly cookie (refresh_token) by the server on login and register — it is not returned in the JSON response body. Your HTTP client must send cookies to use the refresh endpoint. The access_token is returned in the response body and should be stored in memory for use as the Bearer token.