POST /api/auth/register — create a new account

The register endpoint creates a new user account in the system. Before creating the record, the server validates all required fields and checks that the email address is not already in use. Passwords are hashed with bcrypt before storage — never stored in plaintext.

Request

Method: POST
Path: /api/auth/register
Authentication: None required
Content-Type: application/json

Body parameters

name

string

required

A username for the new account. Must not be empty.

string

required

A valid email address. Must not already be registered in the system.

password

string

required

The account password. Must not be empty. Stored as a bcrypt hash (10 salt rounds).

Validation rules

The following rules are enforced by the RegisterValidationRules middleware before the request reaches the controller:

name — must be present and non-empty.
email — must be present, non-empty, and a well-formed email address.
password — must be present and non-empty.

If any rule fails, the server returns a 400 response with a structured list of errors before any database operation occurs.

Response

201 — created

user

object

required

The newly created user record. The password field is excluded from the response.

Hide properties

string

Unique user identifier assigned by the database.

nombre

string

User’s first name (empty string if not provided at registration).

apellido

string

User’s last name (empty string if not provided).

string

The registered email address.

cedula_rif

string

National ID or tax ID (empty string if not provided).

telefono

string

Phone number (empty string if not provided).

cargo

string

Job title (empty string if not provided).

departamento

string

Department (empty string if not provided).

estatus

string

Initial account status set by the system.

created_at

string

ISO 8601 timestamp of account creation.

updated_at

string

ISO 8601 timestamp of the last update.

Registration does not return a JWT token. After registering, call POST /api/auth/login with the same credentials to obtain a token.

Examples

curl --request POST \
  --url http://localhost:7780/api/auth/register \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "mariagonzalez",
    "email": "[email protected]",
    "password": "s3cur3P@ss"
  }'

Success response

201

{
  "user": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "nombre": "",
    "apellido": "",
    "email": "[email protected]",
    "cedula_rif": "",
    "telefono": "",
    "cargo": "",
    "departamento": "",
    "estatus": "activo",
    "created_at": "2024-06-01T10:00:00.000Z",
    "updated_at": "2024-06-01T10:00:00.000Z"
  }
}

Error responses

400

{
  "errors": [
    {
      "field": "email",
      "message": "El email es requerida"
    },
    {
      "field": "password",
      "message": "La contraseña es requerida"
    }
  ]
}

409

{
  "message": "El email ya está registrado.",
  "field": "email"
}

500

{
  "message": "Error interno del servidor."
}

Authentication

HR & Users

Business Operations

Banking

Accounting & Reports

POST /api/auth/register — create a new account

Request

Body parameters

Validation rules

Response

201 — created

Examples

Success response

Error responses

Build docs developers (and LLMs) love

Authentication

HR & Users

Business Operations

Banking

Accounting & Reports

Documentation Index

​Request

​Body parameters

​Validation rules

​Response

​201 — created

​Examples

​Success response

​Error responses

Build docs developers (and LLMs) love

Request

Body parameters

Validation rules

Response

201 — created

Examples

Success response

Error responses