For AI agents: markdown of this page — /docs-content-en/entities/tasks/results.md documentation index — /llms.txt
Task results: legacy REST
GET /v1/tasks/:taskId/results
Returns all task results in one call, without pagination: both the results added as text and the results created from chat messages and comments.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
ParametertaskId (path) |
Typenumber | Requiredyes | DescriptionTask ID, a positive integer. List: GET /v1/tasks |
ParameterWITH_USER_INFO (query) |
Typestring | Requiredno | DescriptionY — add userInfo with the author's data to each result. N or omitted — do not add it |
ParameterWITH_FILE_INFO (query) |
Typestring | Requiredno | DescriptionY — add fileInfo with file data to each result. N or omitted — do not add it |
ParameterWITH_PARSED_TEXT (query) |
Typestring | Requiredno | DescriptionY — add parsedText and fileInfo to each result. N or omitted — do not add them |
Examples
curl — personal key
curl -X GET "https://vibecode.bitrix24.com/v1/tasks/4207/results" \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
curl -X GET "https://vibecode.bitrix24.com/v1/tasks/4207/results" \
-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/tasks/4207/results', {
headers: {
'X-Api-Key': 'YOUR_API_KEY',
},
})
const { success, data } = await res.json()
console.log('Results:', data.length)
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/tasks/4207/results', {
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
})
const { success, data } = await res.json()
Response fields
| Field | Type | Description |
|---|---|---|
Fieldsuccess |
Typeboolean | Descriptiontrue if the request succeeded |
Fielddata |
Typearray | DescriptionTask results in descending order of id: the most recently added result comes first. An empty array for a task without results |
Fielddata[].id |
Typenumber | DescriptionResult ID. Needed to update and delete the result |
Fielddata[].taskId |
Typenumber | DescriptionTask ID |
Fielddata[].commentId |
Typenumber | DescriptionID of the comment on the old task card that the result was created from. A result added as text or from a chat message has 0. List: GET /v1/tasks/:taskId/comments |
Fielddata[].createdBy |
Typenumber | DescriptionID of the employee who added the result. List: GET /v1/users |
Fielddata[].createdAt |
Typestring | DescriptionCreation date and time in ISO 8601 format with a time zone offset, for example 2026-10-19T14:36:12+00:00. A result created from a comment has the date of the comment, not of the call |
Fielddata[].updatedAt |
Typestring | DescriptionDate and time of the last change, in the same format |
Fielddata[].status |
Typenumber | DescriptionResult status: 0 — open, 1 — closed |
Fielddata[].text |
Typestring | DescriptionResult text. May contain BB code markup |
Fielddata[].formattedText |
Typestring | DescriptionResult text with the BB code markup converted to HTML: [b]Report[/b] comes back as <b>Report</b> |
Fielddata[].files |
Typearray | DescriptionIDs of the result files. A result without files has an empty array. File data is in fileInfo |
Fielddata[].userInfo |
Typeobject | DescriptionOnly with WITH_USER_INFO=Y. Author data; the object key is the author ID from createdBy |
Fielddata[].userInfo.<id>.id |
Typestring | DescriptionAuthor ID as a string |
Fielddata[].userInfo.<id>.name |
Typestring | DescriptionFirst name |
Fielddata[].userInfo.<id>.secondName |
Typestring | null | DescriptionMiddle name. null if not filled in |
Fielddata[].userInfo.<id>.lastName |
Typestring | DescriptionLast name |
Fielddata[].userInfo.<id>.formattedName |
Typestring | DescriptionFirst and last name for display |
Fielddata[].userInfo.<id>.avatar |
Typestring | DescriptionURL of the employee's photo |
Fielddata[].fileInfo |
Typeobject | DescriptionOnly with WITH_FILE_INFO=Y or WITH_PARSED_TEXT=Y. File data for the result; the object key is the file ID. A result without files has an empty array [] |
Fielddata[].parsedText |
Typestring | DescriptionOnly with WITH_PARSED_TEXT=Y. Result text. For a result without files, it matches text |
Response example
{
"success": true,
"data": [
{
"id": 29,
"taskId": 4207,
"commentId": 0,
"createdBy": 1295,
"createdAt": "2026-10-19T14:36:12+00:00",
"updatedAt": "2026-10-19T14:36:12+00:00",
"status": 0,
"text": "Quarterly report approved",
"formattedText": "Quarterly report approved",
"files": []
},
{
"id": 27,
"taskId": 4207,
"commentId": 0,
"createdBy": 1295,
"createdAt": "2026-10-19T14:36:11+00:00",
"updatedAt": "2026-10-19T14:36:11+00:00",
"status": 0,
"text": "Draft report sent for approval",
"formattedText": "Draft report sent for approval",
"files": []
}
]
}
Error response example
400 — the flag value is neither Y nor N:
{
"success": false,
"error": {
"code": "INVALID_PARAMS",
"message": "WITH_USER_INFO must be Y or N"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| HTTP400 | CodeINVALID_PARAMS |
DescriptiontaskId is not a positive integer. Message: taskId must be a positive integer |
| HTTP400 | CodeINVALID_PARAMS |
DescriptionThe query string contains a parameter that is not in the "Parameters" table. The name is case-sensitive: with_user_info is rejected too. Message: query contains unsupported fields |
| HTTP400 | CodeINVALID_PARAMS |
DescriptionThe flag value is neither Y nor N. The message names the flag, for example WITH_USER_INFO must be Y or N |
| HTTP401 | CodeMISSING_API_KEY |
DescriptionThe X-Api-Key header is missing |
| HTTP401 | CodeTOKEN_MISSING |
DescriptionThe key has no Bitrix24 tokens |
| HTTP403 | CodeSCOPE_DENIED |
DescriptionThe key has no task scope |
| HTTP422 | CodeBITRIX_ERROR |
DescriptionThe employee on whose behalf the call is made cannot read the task. Message: Access denied. |
| HTTP429 | CodeRATE_LIMITED |
DescriptionRequest rate exceeded. The effective cap is in the x-ratelimit-limit header |
Full list of common API errors — Errors.
Known specifics
REST 3.0 results come back here in a different shape. The author is in createdBy, not authorId, and the status is the number 0, not the string open.
The response does not distinguish a task without results from a task that does not exist. For a request with a nonexistent taskId, a Bitrix24 account administrator's key gets 200 with an empty array. To check that the task exists, use GET /v1/tasks/:id.