PARSER GUIDES
Delete Documents
POST
/api/v1/process/{parserId}/documents/delete
Delete documents so their externalId values can be reused on re-upload.
Request body: Provide documentIds and/or externalIds.
- If you send
documentIds,externalIdsis optional. - If you send
externalIds,documentIdsis optional. - You must provide at least one of them.
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
Request Body
application/json
documentIds?array<string\>
Optional list of document UUIDs to delete.
externalIds?array<string\>
Optional list of external IDs to delete documents by externalId.
Response Body
200
application/json
400
application/json
401
application/json
404
application/json
405
application/json
curl -X POST "https://api.PARSER.com/api/v1/process/d1458cd7-8692-488f-8b3f-0fddade05f9c/documents/delete" \ -H "Content-Type: application/json" \ -d '{}'
200400401404405
{
"success": true,
"deleted": 0,
"ids": [
"497f6eca-6276-4993-bfeb-53cbbbba6f08"
]
}
{
"error": true,
"message": "Parser ID mismatch"
}
{
"error": true,
"message": "Parser ID mismatch"
}
{
"error": true,
"message": "Document not found",
"notFound": [
{
"type": "documentId",
"value": "string"
}
]
}
{
"error": true,
"message": "Parser ID mismatch"
}
Reprocess Document POSTRe-run extraction for an already uploaded document (useful after adding new parser fields). Reprocessing uses the parser's current settings. If the parser has document type rules enabled, PARSER checks the document type again before extraction. The document can return to the \skipped\ status when the current rule says it should not be processed. \*\*Request body:\*\* Provide exactly one of \documentId\ or \externalId\. - \documentId\ and \externalId\ cannot be sent together. - If neither is provided, the API returns \400\.Open guide →
List Classifiers GETList document classifiers available to the API key's team. Parser schema, fields, exports, and review settings are not included.Open guide →