Skip to main content
GET
/
users
curl -X GET https://api.falconalert.com/users \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

{
  "id": "1",
  "email": "user@example.com",
  "name": "John Doe",
  "username": "johndoe_123",
  "password": "55e1ebd3ebe4f1b46a5ccc9866d",
  "salt": "432423",
  "image_path": "profile-pictures/default.jpg",
  "role_id": 1,
  "created_at": "2025-09-25T12:14:44.000Z",
  "updated_at": "2025-10-24T01:45:55.000Z"
}

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/4rt21/backend-proyecto/llms.txt

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

​
Authentication

This endpoint requires a valid JWT Bearer token. The profile returned corresponds to the authenticated user.
​
Authorization
string
required
Bearer token for authenticationFormat: Bearer <your_access_token>

​
Response

​
id
string
Unique user identifier
​
email
string
User’s email address
​
name
string
User’s full name
​
password
string
Hashed password (for security)
​
salt
string
Password salt used for hashing
​
image_path
string
Path to user’s profile image
​
role_id
number
User’s role identifier
  • 1 - Regular user
  • 2 - Admin user
​
created_at
string
Account creation timestamp (ISO 8601 format)
​
updated_at
string
Last profile update timestamp (ISO 8601 format)
​
username
string
User’s unique username
curl -X GET https://api.falconalert.com/users \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

{
  "id": "1",
  "email": "user@example.com",
  "name": "John Doe",
  "username": "johndoe_123",
  "password": "55e1ebd3ebe4f1b46a5ccc9866d",
  "salt": "432423",
  "image_path": "profile-pictures/default.jpg",
  "role_id": 1,
  "created_at": "2025-09-25T12:14:44.000Z",
  "updated_at": "2025-10-24T01:45:55.000Z"
}

​
Error Responses

Status CodeDescription
401Unauthorized - Invalid or missing JWT token

​
Notes

  • The password field is returned as a hashed value for security purposes
  • The salt is used internally for password hashing and should not be displayed to end users
  • Profile information is specific to the authenticated user making the request

Build docs developers (and LLMs) love

Get started for freeTalk to us