For AI agents: markdown of this page — /docs-content-en/timeline-logs/logs/get.md documentation index — /llms.txt

Get an entry

GET /v1/timeline-logs/:id

Returns a single log entry by its ID.

Parameters

Parameter Type Required Description
id (path) number yes Log entry ID. Get a list of IDs — GET /v1/timeline-logs

Examples

curl — personal key

Terminal 
curl https://vibecode.bitrix24.com/v1/timeline-logs/5012 \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

Terminal 
curl https://vibecode.bitrix24.com/v1/timeline-logs/5012 \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"

JavaScript — personal key

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/timeline-logs/5012', {
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})

const { success, data } = await res.json()
console.log(data.title, data.text)

JavaScript — OAuth application

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/timeline-logs/5012', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

const { success, data } = await res.json()

Response fields

Field Type Description
id number Log entry ID
created datetime Creation date, ISO 8601 with the Bitrix24 account timezone
authorId number Author ID. User data by ID: GET /v1/users/:id
title string Title
text string Entry text
iconCode string Icon code (or "" if not set)

Response example

JSON 
{
  "success": true,
  "data": {
    "id": 5012,
    "created": "2026-04-27T10:00:00+00:00",
    "authorId": 1,
    "title": "AI agent processed the request",
    "text": "Customer data analyzed. Recommendation: Enterprise plan.",
    "iconCode": ""
  }
}

Error response example

404 — entry not found:

JSON 
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "Timeline logmessage not found for id `99999999`"
  }
}

Errors

HTTP Code Description
400 INVALID_PARAMS id is not a positive integer
404 ENTITY_NOT_FOUND The log entry with the given id does not exist — Bitrix24 returned a NOT_FOUND error
404 NOT_FOUND Bitrix24 returned a successful response, but the entry object turned out to be empty
403 SCOPE_DENIED The API key does not have the crm scope
401 TOKEN_MISSING The API key has no configured tokens

Full list of common API errors — Errors.

See also