Oasis Liquido’s authentication endpoints handle the full identity lifecycle: account creation, credential verification, token renewal, and session termination. All tokens are JWTs signed with HS256. The access token has a short expiry; use the refresh token to obtain a new one without re-prompting the user.Documentation 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.
POST /api/v1/auth/register
Create a new user account. On success, returns the created user object and anaccess_token in the response body. The refresh_token is set as an httpOnly cookie — it is not in the JSON response.
Request body
A valid, unique email address. Used for login and account recovery.
The user’s plaintext password. Stored as a bcrypt hash.
The user’s full display name.
Optional contact phone number.
The user’s role. Accepted values:
admin, doctor, receptionist, patient, pharmacy_manager, delivery_driver. Defaults to patient if omitted.curl example
POST /api/v1/auth/login
Authenticate with email and password. Returns anaccess_token in the response body. The refresh_token is set as an httpOnly cookie named refresh_token — it is not in the JSON response.
Request body
The registered email address.
The account password.
curl example
POST /api/v1/auth/refresh
Exchange a valid refresh token for a newaccess_token and refresh_token pair. The server reads the refresh token from the refresh_token httpOnly cookie set during login or register. As a fallback, you may also pass it in the request body.
Request body (optional fallback)
The refresh token as a fallback if the httpOnly cookie is not available. In browser environments, the cookie is sent automatically.
curl example (cookie-based)
curl example (body fallback)
POST /api/v1/auth/logout
Invalidate the current session. Requires a valid Bearer token. No request body is needed.curl example
GET /api/v1/auth/me
Return the full profile of the currently authenticated user, including any role-specific nested profile (e.g.,doctor_profile, patient_profile).
curl example
Response fields
UUID of the user.
The user’s email address.
The user’s full name.
The user’s role. One of:
admin, doctor, receptionist, patient, pharmacy_manager, delivery_driver.Optional phone number.
Optional URL to the user’s avatar image.
Whether the account is active.
ISO 8601 timestamp of account creation.
ISO 8601 timestamp of last update.
Present when
role is doctor.Present when
role is patient.