Get Review Item
Fetch one review record with GET /v1/review/:id: overall confidence, the low-confidence fields that need attention, field decisions, and review comments.
GET /v1/review/:id retrieves the full detail of a single Record Review item: a validation record awaiting or having completed record-level human review. Beyond the list-level fields, the detail adds field_decisions (per-field review decisions), low_confidence_fields (the flagged fields with their values and scores), and review_comment. This is the data needed to build custom review interfaces.
low_confidence_fields is an array of objects, not bare field names. Each entry carries field_id, field_name, the extraction confidence for that field, the extracted value itself, and the expected_type from the schema. Fields land here when their extraction confidence fell below 0.85 at run completion, so the array gives a reviewer everything needed to judge a flagged value without a second lookup — the questionable value and what type the schema expected it to be.
field_decisions is an object keyed by field id, each value holding a status (approved or rejected) and an optional comment. It is populated by the platform's partial-approval flow, where a reviewer accepts some fields and rejects others; such records carry the overall status partial. Through the public API the object is read-only — [POST /v1/review/:id/action](review-action) records whole-record decisions and does not write per-field entries.
To show reviewers the actual extracted record alongside the flags, join outward: run_id and document_id identify the result row — fetch it via the run's results endpoint ([GET /v1/jobs/:id/results](get-job-results)) — and document_id also keys the source file and its OCR text for side-by-side display. A typical review UI fetches this detail, highlights the low_confidence_fields entries against the full record, and submits one action call with the verdict.
A 404 from this endpoint means the record id does not exist in your workspace — or that the record's source document is hidden from the API key's minting user by source-visibility rules. The two cases are deliberately indistinguishable, so treat 404 as "not yours to see" rather than proof of deletion. The id must be a well-formed UUID; anything else fails validation with a 400 before lookup.
low_confidence_fields array lists the specific fields that fell below the confidence threshold, with their extracted values and expected types. Use it to highlight problematic cells in your review UI — it is why the record needs eyes on it./v1/review/:idPath parameters
curl
curl -s https://api.talonic.com/v1/review/a1b2c3d4-e5f6-7890-abcd-ef1234567890 \
-H "Authorization: Bearer tlnc_your_api_key"Response
Response fields
Response
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"run_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
"document_id": "c3d4e5f6-a7b8-9012-cdef-123456789012",
"schema_id": "d4e5f6a7-b8c9-0123-defa-234567890123",
"status": "pending",
"overall_confidence": 0.72,
"assigned_to": null,
"reviewed_by": null,
"reviewed_at": null,
"created_at": "2026-08-12T09:00:00.000Z",
"links": {
"self": "/v1/review/a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"action": "/v1/review/a1b2c3d4-e5f6-7890-abcd-ef1234567890/action"
},
"field_decisions": {},
"low_confidence_fields": [
{
"field_id": "d81c2f4a-1b2c-4d5e-8f90-1a2b3c4d5e6f",
"field_name": "total_amount",
"confidence": 0.62,
"value": "1.284,50",
"expected_type": "number"
}
],
"review_comment": null
}Errors
Error responses
Use the low_confidence_fields array to highlight problematic cells in your review UI before calling POST /v1/review/:id/action. On records already actioned in the platform, field_decisions and review_comment show what the reviewer decided — useful for syncing decisions into an external system of record after the fact.