Reclassify as Customer PO

POST 
/api/purchase-invoices/ocr/:purchase_extraction_id/reclassify-as-customer-po

Reclassify a Supplier Invoice OCR extraction as a Customer PO. Used when an inbound email was routed to invoices@ but the attached PDF is actually a customer purchase order — the inverse of POST /api/sales-orders/ocr/{id}/reclassify-as-supplier-invoice.

Required scope: orders:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Copies the file_path, header_data, lines_data, and source email metadata (source, source_email_from, source_email_subject, source_email_recipient) into a new SalesOrderOcrExtraction (status: pending_review). Marks the original PurchaseInvoiceOcrExtraction as 'rejected' with an error_message that references the new extraction ID, preserving an audit trail.

Returns 422 if the extraction is in 'confirmed' status (confirmed extractions cannot be reclassified).

Response 200:

{
  "message": "Reclassified as customer PO.",
  "data": { "sales_order_extraction_id": 42 }
}

The frontend should redirect to /orders/sales-orders/ocr/{id} for the user to continue review.

Request

Responses

200

Successful response

401

Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.

403

Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.

404

Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.

422

Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.

429

Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.