Extract structured data

Extract needs a document and a schema. A schema describes the fields and types you want returned.

Extract directly from a document

Use this when you have a file and want structured data in one request. Set UNSTRUCTURED_API_KEY to your API key and replace the file path.

export UNSTRUCTURED_API_KEY="your-api-key"

curl https://transform.unstructured.io/api/v2/extract \
  -H "unstructured-api-key: $UNSTRUCTURED_API_KEY" \
  -F "input=@document.pdf" \
  --form-string 'schema={"type":"object","properties":{"invoice_number":{"type":"string"}},"required":["invoice_number"],"additionalProperties":false}'

Extract from a completed Parse

Reuse a Parse when you want to extract different fields from content you already processed. Set PARSE_ID to its completed result’s id. This shell example also requires jq.

curl https://transform.unstructured.io/api/v2/extract \
  -H "unstructured-api-key: $UNSTRUCTURED_API_KEY" \
  -H "Content-Type: application/json" \
  --data "$(jq -n --arg id "$PARSE_ID" '{parse_id: $id, schema: {"type":"object","properties":{"invoice_number":{"type":"string"}},"required":["invoice_number"],"additionalProperties":false}}')"

Use JSON for parse_id requests and multipart form data for input or file_id. Send one document source per request. A missing document source or invalid combination requires correcting the request; see error codes and fixes. See Chain Parse and Extract for the complete sequence.

Read the result

For a completed HTTP 200 result, read extracted_data[i].data. The captured response contains invoice_number: "DEMO-001" and total: 10.0. HTTP 202 means the job continues. Keep the complete Location URL, including its query parameters, and follow request progress. Do not reconstruct an extraction retrieval URL from the job ID alone. See schema guidance and the endpoint reference.

​Extract directly from a document

​Extract from a completed Parse

​Read the result

Extract directly from a document

Extract from a completed Parse

Read the result