Skip to main content

Get Extraction Data

Fetch just the extracted key-value data from an extraction with GET /v1/extractions/:id/data. Returns clean JSON by default or a downloadable CSV file.

The Get Extraction Data endpoint, GET /v1/extractions/:id/data, retrieves only the extracted field values from an extraction, without metadata, confidence scores, or processing details. This is the lightest-weight endpoint for consuming extraction output, and it is ideal for downstream integrations that only need the structured data as JSON or CSV.

Use ?format=csv to download the data as a CSV file. The response Content-Type changes to text/csv and includes a Content-Disposition header for browser downloads.
GET/v1/extractions/:id/data

Query parameters

formatstringResponse format: json or csv. Default: "json"
Set ?format=csv to receive the data as a downloadable CSV file. The response Content-Type will be text/csv.

curl

Response

Response fields

(field_name)anyEach key is an extracted field name; value is the extracted value. Shape matches the schema used during extraction.

Response (JSON)

{
  "vendor_name": "Acme Corp",
  "invoice_number": "INV-2024-0847",
  "total_amount": 14250.00,
  "due_date": "2024-03-15"
}

Most integrations call this endpoint to feed extraction output into downstream systems (CRMs, ERPs, data warehouses) that only need the raw key-value data. A typical workflow is to extract a document, then call this endpoint with the extraction_id from the response to get a clean data payload without metadata overhead.

The response is a flat JSON object where each key is a field name and each value is the extracted value, typed according to the schema (strings, numbers, dates, arrays). Use ?format=csv to download the same data as a CSV file with field names as headers — the Content-Disposition header provides a suggested filename.

Pair this with GET /v1/extractions/:id when you also need confidence scores, locked field status, or processing metadata. Note that the response shape matches the schema used during extraction — if no schema was provided, auto-discovered field names are used as keys.

Errors

Error responses

401unauthorizedMissing or invalid API key.
404not_foundNo extraction with this ID exists for your organization.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.