Lists the source items a document was built from.
Normalized provenance: a stable key per item in whatever produced it, and what that item contributed — created, extended, confirmed, or arrived with a document that consolidation folded in. The keys are returned, never the items: resolving one is the source system's call under its own authorization, so a caller who may read the article does not thereby gain the transcript. What an agent review found also names the conversation it was found in (`conversation`), as ids to open it by in the agent's Conversations tab, where access to the agent is checked, and where the answer came from in it (`conversation.answerSource`): a team member's reply or a tool result.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The knowledge base id.
uuidThe document id.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/knowledgeBases/497f6eca-6276-4993-bfeb-53cbbbba6f08/documents/497f6eca-6276-4993-bfeb-53cbbbba6f08/evidence"[
{
"id": "00000000-0000-0000-0000-000000000000",
"knowledgeDocumentId": "00000000-0000-0000-0000-000000000000",
"knowledgeSourceId": "00000000-0000-0000-0000-000000000000",
"sourceItemKey": "string",
"sourceVersion": "string",
"sourceUrl": "string",
"ledgerItemId": "00000000-0000-0000-0000-000000000000",
"executionRecordId": "00000000-0000-0000-0000-000000000000",
"contributionKind": "CREATED",
"capturedAt": 0,
"conversation": {
"agentId": "string",
"topicId": "00000000-0000-0000-0000-000000000000",
"runId": "00000000-0000-0000-0000-000000000000",
"participantId": "00000000-0000-0000-0000-000000000000",
"channelAddress": "string",
"answerSource": "string",
"whatHappened": "string",
"teamAnswer": {
"question": "string",
"answer": "string",
"turns": []
}
}
}
]{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}