Skip to main content

Review Batch

Batch approve or reject review items with POST /v1/review/batch. One action applies to all IDs, with per-record outcomes reported in the results array.

POST /v1/review/batch applies one review decision (approve or reject) to many review items in a single API call. This is the fastest way to clear backlogs when you have high-confidence items that can be bulk-approved, or when rejecting a batch of items from a failed extraction run.

The batch endpoint processes items independently. If some items fail (e.g. not found), the remaining items are still processed. Check the results array for per-item outcomes.
POST/v1/review/batch

Body parameters

ids*string[]Non-empty array of review item UUIDs.
action*stringAction to apply to every ID: `approve` or `reject`.

Response

Response fields

processedintegerNumber of records successfully actioned.
failedintegerNumber of records that could not be actioned.
resultsarrayPer-record outcome array.
results[].idstringReview record UUID.
results[].statusstringResulting status (approved, rejected) or "error" if the record was not found.
results[].errorstringError code if the record could not be actioned (e.g. not_found).

Response

{
  "processed": 2,
  "failed": 0,
  "results": [
    { "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "status": "approved" },
    { "id": "b2c3d4e5-f6a7-8901-bcde-f12345678901", "status": "approved" }
  ]
}

Errors

Error responses

401unauthorizedMissing or invalid API key.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

A common pattern is to first call GET /v1/review?status=pending to collect IDs, filter client-side by overall_confidence above a safe threshold, then batch-approve those IDs here. Check the results array for per-item outcomes: IDs that cannot be found return an error entry but do not block the rest of the batch.

Related

Approve or Reject an Item
Review Queue Statistics
List Review Items