Send booking feedback

Your accountant adjusts an account or VAT code on the proposal. Product-wise the ledger stays yours; Docpier records the correction. Architecturally this is a batch POST of complete booking resources keyed by bookingJobId, not by a Docmind documentId.

HTTP status is 200; each item has SUCCESS or ERROR.

POST/api/docbooks/v1/feedback

Tip

resourceId is the Docbooks bookingJobId (not a Docmind documentId). resource is the complete corrected area, same shape as the GET.

Authentication

Authorizationstringrequired

Bearer token with scope docbooks.bookings.

Body

dataFeedbackItem[]bodyrequired

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

data[].resourceIdstringbodyrequired

bookingJobId from submit / GET.

data[].resourceobjectbodyrequired

Complete corrected booking payload.

data[].reasonsFieldReason[]body

Optional per-field codes (MISSING, INCORRECT_VALUE, OTHER, and the other values on the released enum).

Note

Schema: Docbooks API reference (Feedback). Docmind extraction feedback is a different POST — Send extraction feedback.

Request

cURL

curl -X POST 'https://stage.docpier.io/api/docbooks/v1/feedback' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "data": [
      {
        "resourceId": "01HXYZBOOKING0000000001",
        "resource": {
          "bookingJobId": "01HXYZBOOKING0000000001",
          "status": "COMPLETED"
        },
        "comments": "Corrected account on line 1"
      }
    ]
  }'

Replace resource with the full object you received on GET, after edits. A stub object will fail validation.

Response

{
    "workspaceId": "01HXYZDOCBOOKSWS0000001",
    "data": [
        {
            "resourceId": "01HXYZBOOKING0000000001",
            "status": "SUCCESS"
        }
    ]
}

Authentication​

Body​

Authentication

Body