Skip to main content

Export Decision Log

Export the field-review decision log as an RFC 4180 CSV (UTF-8 with BOM, Excel-friendly) for customer handover. Filter to one pipeline or export org-wide.

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, 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.

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

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)

Errors

Error responses

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