Reads what one batch question was answered with, item by item.
One row per item the batch held: the value it was handed back (`answer`) beside what the person gave for it (`given`) — the sheet cell or the words in their message, as the agent conducting the conversation copied them; a direct question's reply; a form's field — and where the item is now. The two differ exactly where an answer went wrong, which is the question this read exists for. `topicAgentId` is the agent the batch's conversation belongs to — the stage's asking agent, not the one that talked to the person (`conductorAgentId`) — and is the agent to read its transcript under. A batch answered before answers were recorded has `recorded` false: its values are read back off its conversation's result, with no per-item time.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The trigger identifier.
uuidThe batch identifier.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/batches/497f6eca-6276-4993-bfeb-53cbbbba6f08/answers"{
"batchId": "00000000-0000-0000-0000-000000000000",
"stageId": "string",
"status": "OPEN",
"topicId": "00000000-0000-0000-0000-000000000000",
"topicAgentId": "string",
"conductorAgentId": "string",
"answeredWhenPath": "string",
"resolvedAt": 0,
"recorded": false,
"items": [
{
"itemKey": "string",
"itemId": "00000000-0000-0000-0000-000000000000",
"label": "string",
"given": null,
"givenIsReply": false,
"answer": null,
"current": null,
"answeredAt": 0,
"answeredBy": "string",
"stageId": "string",
"status": "READY",
"lastError": "string",
"terminalAt": 0
}
]
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists what the automation is waiting on a human for.
Each batch is one shared question with a set of items waiting on its answer. It is the operator's awaiting-human entry, and its waiting count is the number an operator reads.
Calls off an open batch.
The items go back to READY at the stage that asked, so a later pass re-batches them — cancelling the question is not the same as deciding the items no longer need one. The response's `returnedCount` is how many went back; its `waitingCount` is read after the cancel and is 0. Returns 409 when the batch has already been answered or expired.