For AI agents: markdown of this page — /docs-content-en/entities/users/get.md documentation index — /llms.txt
Get employee
GET /v1/users/:id
Returns the employee data by ID with all fields, including user (UF_*) fields.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
id (path) |
number | yes | Employee ID |
Examples
curl — personal key
curl "https://vibecode.bitrix24.com/v1/users/29" \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
curl "https://vibecode.bitrix24.com/v1/users/29" \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN"
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/users/29', {
headers: {
'X-Api-Key': 'YOUR_API_KEY',
},
})
const { success, data } = await res.json()
console.log(`${data.name} ${data.lastName} — ${data.email}`)
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/users/29', {
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
})
const { success, data } = await res.json()
Response fields
The employee object with all fields — see Employee fields.
Response example
{
"success": true,
"data": {
"id": 29,
"xmlId": "28936832",
"active": true,
"name": "John",
"lastName": "Brown",
"email": "john.brown@example.com",
"lastLogin": "2026-03-30T14:39:25.000Z",
"dateRegister": "2020-04-23T00:00:00.000Z",
"timeZone": "UTC",
"isOnline": false,
"timestampX": {},
"lastActivityDate": {},
"personalPhoto": "https://cdn.bitrix24.com/.../photo.png",
"departmentId": [1],
"userType": "employee"
}
}
Error response example
404 — employee not found:
{
"success": false,
"error": {
"code": "ENTITY_NOT_FOUND",
"message": "user 999999999 not found"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 400 | INVALID_ID |
:id is not a positive integer |
| 401 | TOKEN_MISSING |
The API key has no configured tokens |
| 403 | SCOPE_DENIED |
The API key lacks the user scope |
| 404 | ENTITY_NOT_FOUND |
No employee with this ID found, or it is deactivated and unavailable to the current key |
Full list of common API errors — Errors.
Known specifics
WORK_* fields and some PERSONAL_* fields arrive in UPPER_SNAKE_CASE. WORK_COMPANY, WORK_DEPARTMENT, WORK_WWW, WORK_FAX, WORK_CITY, WORK_STATE, WORK_ZIP, WORK_COUNTRY and the like; PERSONAL_STATE, PERSONAL_ZIP, PERSONAL_COUNTRY, PERSONAL_MAILBOX, PERSONAL_NOTES — in their original Bitrix24 names. Bitrix24 account UF fields also keep their names. Standard fields (name, email, active, timeZone, userType, departmentId, etc.) — camelCase.
See also
- Employee fields — all fields
- List employees — search with filters
- Update employee — changing fields
- Limits and optimization