Get extraction data of an Order in JSON format

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 it must read a single CSA profile. The extraction project's export mapping must target that profile. A template without columns must have a transform; otherwise the request returns 400 with a message naming the problem.

The fund does not need an SA profile configured. Mapped extraction values are sent directly to the template without conversion or validation against the fund's CSA version.

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 template's CSA profile using the extraction mapping's declared CSA version 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 compatible mapping to the template's CSA profile, a referenced extraction record that no longer exists, or a transient transform-infrastructure failure that persists after retries.

Each entry's files lists the documents the data was extracted from. fileId matches files[].id in GetOrderSupportingDoc, so an entry can be joined to the supporting doc it came from.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The Anduin ID of the Order object, or your custom ID

Body Params
string

Optional CSA data template ID linked to the fund. The template must read one CSA profile supported by the extraction project's export mapping. A template without columns needs a transform. Invalid configurations return 400. The fund does not need a CSA profile configured. Omit it (empty body {}) to export the raw data with the default template.

Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json