Re-process a failed document
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/force-reparse/"
payload = { "lift_cell_limit": False }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({lift_cell_limit: false})
};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/force-reparse/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request POST \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/force-reparse/ \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"lift_cell_limit": false
}
'{
"message": "<string>",
"extraction_flows_dispatched": 123,
"document": {}
}{
"error": "User not found"
}{
"error": "Authentication credentials were not provided."
}{
"error": "You do not have permission to perform this action."
}Documents
Re-process a failed document
Re-queue one failed document for processing. Successful nodes stay cached, so
processing resumes at the failure. Requires permission to manage sources.
With lift_cell_limit (“Process anyway”), a spreadsheet refused over the cell limit
(failure_reason: too_many_cells) is parsed in full, as are its later re-parses
(cell_limit_lifted on the document).
POST
/
projects
/
{project_id}
/
documents
/
{document_id}
/
force-reparse
/
Re-process a failed document
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/force-reparse/"
payload = { "lift_cell_limit": False }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({lift_cell_limit: false})
};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/force-reparse/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request POST \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/force-reparse/ \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"lift_cell_limit": false
}
'{
"message": "<string>",
"extraction_flows_dispatched": 123,
"document": {}
}{
"error": "User not found"
}{
"error": "Authentication credentials were not provided."
}{
"error": "You do not have permission to perform this action."
}Authorizations
BearerAuthTokenAuth
Use Authorization: Bearer <token>. The token is either a user token / OAuth access
token, or a service-account API key (cfk_...). A key is valid on every endpoint and
acts as its service account, an organization member with per-store permissions.
Refused keys answer 403 with Invalid API key., API key revoked.,
API key expired. or API key disabled..
Path Parameters
Body
application/json