Re-scan Extraction

POST 
/api/landed-cost-invoices/ocr/:landed_cost_extraction_id/rescan

Re-run Azure Document Intelligence OCR on the original PDF (e.g., after Azure model improvements, or to retry a failed extraction). Async — returns a tracked_job_log_id for progress tracking via the tracked job log endpoints.

Required scope: purchase-orders:write

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

Refuses (422) if the extraction is in confirmed status, or if the original file_path is missing.

Response 200:

{
  "data": {
    "extraction_id": 18,
    "tracked_job_log_id": 9311,
    "status": "processing"
  },
  "message": "Re-scan started."
}

Response 422 (already confirmed):

{ "message": "Confirmed extractions cannot be re-scanned." }

Response 422 (file missing):

{ "message": "Cannot re-scan — original file is no longer available." }

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.