## Get comment

`GET /v1/timelines/:id`

Returns a single timeline comment by its ID.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|---------|
| `id` (path) | number | yes | Comment ID. Get the list of IDs — [`GET /v1/timelines`](/docs/entities/timelines/list) |

## Examples

### curl — personal key

```bash
curl "https://vibecode.bitrix24.com/v1/timelines/66303" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl "https://vibecode.bitrix24.com/v1/timelines/66303" \
  -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/timelines/66303', {
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

const { success, data } = await res.json()
console.log('Comment:', data.comment)
```

### JavaScript — OAuth application

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

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

## Response fields

| Field | Type | Description |
|------|-----|---------|
| `success` | boolean | Always `true` on success |
| `data` | object | The comment. Field descriptions — see [Comment fields](/docs/entities/timelines/fields) |
| `data.id` | number | Comment ID |
| `data.entityType` | string | Type of the parent CRM record in lowercase: `deal`, `lead`, `contact`, `company`, `dynamic_<entityTypeId>` |
| `data.entityId` | number | Parent record ID |
| `data.comment` | string | Comment text |
| `data.authorId` | number | Author ID. User data: `GET /v1/users/:id` |
| `data.createdAt` | datetime | Creation date, ISO 8601 in UTC |
| `data.FILES` | object | Attached files — only if the comment has any. The key is the Drive file ID and the value holds the file metadata, whose structure is shown on the [Add comment](/docs/entities/timelines/create) page. Download a file through [`GET /v1/timelines/:commentId/files/:fileRef/download`](/docs/entities/timelines/file-download) |

## Response example

```json
{
  "success": true,
  "data": {
    "id": 66303,
    "entityId": 575,
    "entityType": "deal",
    "comment": "First contact: the client showed interest in the offer",
    "authorId": 1,
    "createdAt": "2026-04-24T12:34:05.000Z"
  }
}
```

## Error response example

404 — comment not found:

```json
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "Not found."
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 404 | `ENTITY_NOT_FOUND` | A comment with the specified ID does not exist |
| 403 | `SCOPE_DENIED` | The API key lacks the `crm` scope |
| 401 | `TOKEN_MISSING` | The API key has no configured tokens |

Full list of common API errors — [Errors](/docs/errors).

## See also

- [List comments](/docs/entities/timelines/list)
- [Update comment](/docs/entities/timelines/update)
- [Delete comment](/docs/entities/timelines/delete)
- [Comment fields](/docs/entities/timelines/fields)
- [Limits and optimization](/docs/optimization)