Skip to main content

Export Decision Log

Export the field review decision log as an RFC 4180 CSV, UTF-8 with BOM so it opens cleanly in Excel. Filter to one pipeline or export the org-wide history.

Export the field-review decision log as a CSV file for customer handover. The export is the same per-field decision history as the JSON decisions endpoint, minus advisory recommend rows, serialized as RFC 4180 CSV with a UTF-8 byte-order mark so it opens cleanly in Excel. Each row is one decision: who decided, the field, the action, the prior and final values, the gate, and the reason. A recommend row carries no authority and never appears in this export — only the confirming or overruling decision does.

Filter to a single run with pipeline_id, or omit it to export the org-wide log across every run. Unlike the JSON list, the CSV is not paginated: it returns the full decision history for the scope in one download, which is what a handover audit needs. The response is sent as a file attachment named field-review-decisions.csv.

The response Content-Type is text/csv; charset=utf-8 and the Content-Disposition header marks it as an attachment, so a browser or HTTP client saves it directly. Use this endpoint when you need the decision trail outside the API, for example to hand a finished run's review history to a customer. This endpoint requires an API key with the read scope.

The CSV is written with a UTF-8 BOM so Excel detects the encoding and renders non-ASCII values correctly. The export is unpaginated: it returns the full decision history for the requested scope.
GET/v1/field-reviews/decisions/export

Query parameters

pipeline_idstringScope to one pipeline run (UUID). Omit for the org-wide log.

curl

curl -s -o field-review-decisions.csv \
  "https://api.talonic.com/v1/field-reviews/decisions/export?pipeline_id=a1b2c3d4-e5f6-7890-abcd-ef1234567890" \
  -H "Authorization: Bearer tlnc_your_api_key"

Response

Response

Content-Typeheadertext/csv; charset=utf-8.
Content-Dispositionheaderattachment; filename="field-review-decisions.csv".
bodytext/csvRFC 4180 CSV with a UTF-8 BOM, one row per decision.

Response (text/csv)

decided_at,decided_by,queue,document,field_key,trigger,stage,action,prior_value,final_value,reason
2024-09-14T11:20:05.000Z,ana@acme.com,Q3 Lease Review,lease_oct.pdf,total_amount,gate,Amount reconciliation,correct,"12,500.00",12500.00,Stripped thousands separator to match field format.

Errors

Error responses

401unauthorizedMissing or invalid API key.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

Frequently asked questions

Why is there a BOM in the CSV?+
The UTF-8 byte-order mark lets Excel detect the encoding so non-ASCII values render correctly. The file is RFC 4180 compliant, so other CSV tools parse it cleanly as well.
Is the CSV export paginated?+
No. Unlike the JSON decisions list, the CSV returns the full decision history for the requested scope in one download, which is what a handover audit needs.
When should I use the CSV export instead of the JSON log?+
Use the CSV when the decision trail leaves the API: handing a finished run's review history to a customer, attaching it to an audit, or analyzing it in a spreadsheet. Use the JSON endpoint when your own code consumes the log.

Related

Decision Log
List Field Reviews