The Users API gives you complete control over user accounts: list all users, look up a single user by ID or by status, create new accounts, update existing ones, and delete records. All write operations go through stored procedures; passwords are hashed with BCrypt before they are persisted.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/jparra-amell/api_solsql/llms.txt
Use this file to discover all available pages before exploring further.
Password hashing behavior
When you create a user, the API always BCrypt-hashes the plain-text password you supply before storing it.When you update a user, the API checks whether the password value you send already begins with
$2a$. If it does, the value is stored as-is — no re-hashing occurs. If it does not start with $2a$, the API treats it as a new plain-text password and hashes it before saving.Endpoints at a glance
GET /api/vw_user
Return all user accounts.
GET /api/vw_user/{id}
Return a single user by their numeric ID. Returns
404 if not found.GET /api/vw_user/status/{status}
Filter users by status. Pass
1 for active accounts or 0 for inactive accounts.POST /api/vw_user
Create a new user. Supply
Name, Email, Password (plain text), and Role.PUT /api/vw_user/{id}
Update an existing user by ID. All fields — including
Status — can be changed.DELETE /api/vw_user/{id}
Delete a user by ID.
User object fields
Every user record contains these fields:| Field | Type | Description |
|---|---|---|
Id | integer | Auto-generated unique identifier. |
Name | string | Full name of the user. |
Email | string | Email address used for login. |
Password | string | BCrypt hash of the user’s password. |
Role | integer | 1 = regular user, 2 = administrator. |
Status | integer | 1 = active, 0 = inactive. |
Created_at | datetime | UTC timestamp of account creation. |