Skip to main content
POST
/
auth
/
login
Login User
curl --request POST \
  --url https://api.example.com/auth/login \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "<string>",
  "password": "<string>"
}
'
{
  "user": {
    "user.id": 123,
    "user.name": "<string>",
    "user.email": "<string>",
    "user.role": "<string>",
    "user.createdAt": "<string>"
  },
  "token": "<string>"
}

​
Overview

Authenticates a user with email and password credentials, returning a JWT token for subsequent authenticated requests. This endpoint is rate-limited to 10 requests per 15-minute window.

​
Authentication

No authentication required. This is a public endpoint.

​
Request Body

​
email
string
required
The user’s email address
​
password
string
required
The user’s password. Must be at least 6 characters long.

​
Request Example

{
  "email": "[email protected]",
  "password": "securePassword123"
}

​
Response

​
user
object
The authenticated user object without sensitive data
​
user.id
integer
Unique user identifier
​
user.name
string
User’s full name
​
user.email
string
User’s email address
​
user.role
string
User’s role (“customer” or “admin”)
​
user.createdAt
string
ISO 8601 timestamp of account creation
​
token
string
JWT access token to be used for authenticated requests. Include this token in the Authorization header as Bearer <token> for subsequent API calls.

​
Response Example

{
  "user": {
    "id": 1,
    "name": "John Doe",
    "email": "[email protected]",
    "role": "customer",
    "createdAt": "2026-03-06T10:30:00.000Z"
  },
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjEiLCJlbWFpbCI6ImpvaG4uZG9lQGV4YW1wbGUuY29tIiwicm9sZSI6ImN1c3RvbWVyIiwiaWF0IjoxNzA5NzI1ODAwfQ.example_signature"
}

​
Error Responses

​
401 Unauthorized

Returned when credentials are invalid. The error message is intentionally generic to avoid revealing whether the user exists. 
{
  "error": "Email o contraseña inválidos"
}

​
400 Bad Request

Returned when validation fails (invalid email format, password too short, missing fields). 
{
  "error": "Validation failed",
  "details": [
    "La contraseña debe tener al menos 6 caracteres"
  ]
}

​
429 Too Many Requests

Returned when rate limit is exceeded (10 requests per 15 minutes). 
{
  "error": "Demasiados intentos. Intenta de nuevo en 15 minutos."
}

​
Using the Token

Once you receive the JWT token, include it in the Authorization header for authenticated requests: 
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

​
Notes

  • The JWT token contains the user’s id, email, and role
  • Passwords are never logged or exposed in responses
  • Failed login attempts do not reveal whether the email exists in the system
  • The token should be stored securely on the client side

Build docs developers (and LLMs) love

Get started for freeTalk to us