PARSERGet Started

PARSER GUIDES

Reprocess Document

POST

/api/v1/parsers/{parserId}/documents/{documentId}/reprocess

Re-run extraction for one existing document using the parser's current settings. If document type rules are enabled, the document is checked again and can return to skipped instead of being extracted.

Authorization

bearerAuth

authorization: <token>

Your API key. Include it directly in the Authorization header as the API key value (e.g., 'authorization: your-api-key-here')

In: header

Path Parameters

parserId — string

The ID of the parser

Format: uuid

documentId — string

The ID of the document

Format: uuid

Response Body

200

application/json

401

application/json

404

application/json

409

application/json

curl -X POST "https://api.PARSER.com/api/v1/parsers/d1458cd7-8692-488f-8b3f-0fddade05f9c/documents/3eb8e281-89b8-4cf0-9397-660794692cef/reprocess"

200401404409

{
  "success": true,
  "documentId": "2b9b1243-3d94-42b0-9515-729c7404e3b7",
  "status": "processing"
}
{
  "error": true,
  "message": "Parser ID mismatch"
}
{
  "error": true,
  "message": "Document not found",
  "notFound": [
    {
      "type": "documentId",
      "value": "string"
    }
  ]
}
{
  "error": true,
  "message": "Parser ID mismatch"
}
Bulk Delete Documents POSTDelete documents by document IDs, external IDs, or both. This is the resource-path equivalent of the existing process delete endpoint.Open guide → List Folders GETList folders for a parser, including document counts and auto-assignment settings.Open guide →