Send extraction feedback

Operators will disagree with an amount, a documentType, or a missing UID. Product-wise this is the quality loop: your UI is the source of truth for the correction. Architecturally you POST the whole corrected document (same shape as GET data[]), not a JSON Patch.

HTTP status is always 200; each item has SUCCESS or ERROR. A FEEDBACK_RECEIVED webhook follows.

POST/v1/workspaces/{workspaceId}/feedback

The per-document PATCH is deprecated. New integrations use this batch POST (1–100 items).

Tip

resource is the complete corrected data area — the same shape you received on GET, not a partial patch.

Authentication

Authorizationstringheaderrequired

Bearer token with scope docmind.capture (today idp.capture).

Path

workspaceIdstringpathrequired

Workspace ULID.

Body

dataFeedbackItem[]bodyrequired

One to 100 items. resourceId must be unique in the batch.

data[].resourceIdstringbodyrequired

The documentId from upload / GET.

data[].resourceobjectbodyrequired

Corrected document, including documentType (for example RECEIPT).

Note

Schema: Submit feedback (Feedback group).

Request

cURL

curl -X POST 'https://idp-stage.docpier.com/api/v1/workspaces/$WORKSPACE_ID/feedback' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "data": [{
      "resourceId": "01HXYZRECEIPT00000001",
      "resource": {
        "documentType": "RECEIPT",
        "documentId": "01HXYZRECEIPT00000001",
        "title": "Quittung Migros",
        "identifications": [{"type": "RECEIPT_NUMBER", "value": "POS-88421"}],
        "grossAmount": {"currency": "CHF", "value": 24.90},
        "paymentMethods": [{"type": "TWINT"}]
      }
    }]
  }'

Response

200

{
    "workspaceId": "04HXYZ123456789ABCDEF",
    "data": [
        {
            "resourceId": "01HXYZRECEIPT00000001",
            "status": "SUCCESS"
        }
    ]
}