Export the extraction data of the Order.

Provide an empty JSON body ({}) to export the raw extracted data with the default template.

Set templateId to a CSA data template ID to export the data shaped by that template. The template must be linked to the fund, and every one of its fields must come from the fund's configured CSA profile (a template with no fields is rejected); otherwise the request returns 400 with a message naming the problem.

extractionData is null when the Order's subscription document has no completed extraction yet — either no extraction request exists or it is still in progress. This is not an error: the response still succeeds and carries supportingDocData, so poll the Order's extraction status and retry once extraction completes.

The response also includes supportingDocData: the extracted data of the Order's supporting documents (AML/KYC and other configured doc types), one entry per extraction request whose extraction has completed — pending review or reviewed. This is the same rule extractionData follows for the subscription document: data is available once extraction completes, whether or not it has been reviewed yet. Without a templateId, each entry is RAW (the doc type's extraction template shape). With a CSA data template ID, each entry is transformed into the fund's CSA profile and shaped by the template (dataFormat = SA_PROFILE); an entry falls back to RAW when the transform cannot be resolved or run for its document type — e.g. no linked extraction workspace, no active table-mapping version, no mapping to the configured CSA profile, a referenced extraction record that no longer exists, or a transient transform-infrastructure failure that persists after retries.