Task results: legacy REST

These four routes call tasks.Task.Result.* through the legacy Bitrix24 REST transport. The API key needs the task (or tasks) scope. VibeCode makes one call and returns its result as data without changing the shape.

POST /v1/task-results/from-comment/:commentId

GET /v1/tasks/:taskId/results

GET /v1/tasks/:taskId/results/first

GET /v1/tasks/:taskId/results/last

HTTP	Route	Bitrix24 method	Bitrix24 parameters
POST	/v1/task-results/from-comment/:commentId	tasks.Task.Result.addFromComment	commentId, optional params from the JSON body
GET	/v1/tasks/:taskId/results	tasks.Task.Result.list	taskId, optional params from the query
GET	/v1/tasks/:taskId/results/first	tasks.Task.Result.getFirst	taskId
GET	/v1/tasks/:taskId/results/last	tasks.Task.Result.getLast	taskId

commentId and taskId must be positive integer IDs. For list, the optional query flags WITH_USER_INFO, WITH_PARSED_TEXT, and WITH_FILE_INFO accept Y or N and are sent to Bitrix24 inside params. For addFromComment, the optional body can be {"params":{"WITH_FILE_INFO":"Y"}}; only this flag is supported, and it is passed through unchanged.

addFromComment addresses legacy forum comments. It does not promise to work with the new task card. This route does not search task chat or call another method if Bitrix24 refuses the request. After an uncertain POST outcome, inspect task results before retrying.

Success has the shape { "success": true, "data": <Bitrix24 result> }. An empty list returns data: []. getFirst and getLast return Bitrix24's { "result": 0 } when there is no result; this is not a 404. addFromComment may return null. VibeCode does not rename the result object's fields.

Invalid IDs, flags, or bodies return 400 INVALID_PARAMS; a missing or invalid key returns 401; missing scope and a write attempt with a READONLY key return 403. Bitrix24 refusals use the standard /v1 handler and may return 422 BITRIX_ERROR, 429 RATE_LIMITED, 502 BITRIX_UNAVAILABLE, or 503 BITRIX_TIMEOUT.