Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/devdavco/backend_1/llms.txt

Use this file to discover all available pages before exploring further.

The Usuarios resource represents registered user accounts in the CoworkingBooking platform. Each user holds a display name, a unique email address, a role identifier, and a password value. Through this API you can list all users, look up a specific user by their integer ID, register a new user account, and permanently remove a user from the system.

​
Base path

/usuarios

​
Endpoints

MethodPathDescription
GET/usuarios/pingHealth check — returns the plain text string "pong"
GET/usuarios/allRetrieve a list of all registered users
GET/usuarios/{id}Fetch a single user by their integer ID
POST/usuarios/createRegister a new user account
DELETE/usuarios/eliminar/{id}Permanently delete a user by ID

​
The Usuario object

Every response that returns user data uses the following shape.
​
id
integer
Auto-generated primary key. Assigned by the database on creation and never changes.
​
nombre
string
The user’s full display name. Maximum 100 characters. Cannot be blank.
​
email
string
The user’s email address. Maximum 150 characters. Must be a valid email format and must be unique across all users — duplicate emails are rejected with a 400 error.
​
password_hash
string
The password value stored for this user. Maximum 255 characters. See the security warning below.
​
rol
string
A free-form role identifier used to differentiate access levels. Common values are "admin" and "usuario", but the field has no server-side enum constraint.

​
Example Usuario object

{
  "id": 1,
  "nombre": "María García",
  "email": "[email protected]",
  "password_hash": "s3cr3tP@ssword",
  "rol": "usuario"
}
password_hash is returned in plain text by every GET endpoint. The server currently stores and returns this value exactly as it was supplied at creation time — no server-side hashing is applied. Before using this API in any production or internet-accessible environment, ensure passwords are hashed client-side (e.g., with bcrypt) before being sent, and review whether returning this field in GET responses is appropriate for your security model.

​
Explore the endpoints

GET /ping

Health check that returns the plain text string "pong".

GET /all

Retrieve a list of all registered users in the system.

GET /{id}

Fetch a single user by their integer ID.

POST /create

Register a new user account with name, email, password, and role.

DELETE /eliminar/{id}

Permanently delete a user account by ID.

Build docs developers (and LLMs) love

Get started for freeTalk to us