Skip to main content
GET
/
api
/
user
/
detail
/
{id}
Get User Details
curl --request GET \
  --url https://api.example.com/api/user/detail/{id}
{
  "code": 123,
  "status": "<string>",
  "user": {
    "id": 123,
    "name": "<string>",
    "surname": "<string>",
    "email": "<string>",
    "role": "<string>",
    "description": "<string>",
    "created_at": "<string>",
    "updated_at": "<string>"
  },
  "message": "<string>"
}

Endpoint

GET /api/user/detail/{id}
This endpoint retrieves detailed information about a user. No authentication is required.

Path Parameters

id
integer
required
The unique identifier of the user to retrieve

Response

code
integer
HTTP status code (200 for success, 404 for not found)
status
string
Status of the request: success or error
user
object
The user object containing all user details
id
integer
User’s unique identifier
name
string
User’s first name
surname
string
User’s last name
email
string
User’s email address
role
string
User’s role (e.g., ROLE_USER)
description
string
User’s profile description (optional)
created_at
string
Timestamp when the user was created
updated_at
string
Timestamp when the user was last updated
message
string
Error message (only present when status is error)

Request Example

curl -X GET "https://api.example.com/api/user/detail/1"

Response Examples

{
  "code": 200,
  "status": "success",
  "user": {
    "id": 1,
    "name": "John",
    "surname": "Doe",
    "email": "[email protected]",
    "role": "ROLE_USER",
    "description": "Full-stack developer",
    "created_at": "2024-01-15T10:30:00.000000Z",
    "updated_at": "2024-01-20T14:45:00.000000Z"
  }
}
This endpoint does not require authentication. The user’s password and remember_token fields are automatically hidden from the response.

Build docs developers (and LLMs) love