Delete document
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text)const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request DELETE \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/ \
--header 'Authorization: Bearer <token>'{
"error": "Authentication credentials were not provided."
}{
"error": "You do not have permission to perform this action."
}{
"error": "Not found."
}Documents
Delete document
Delete a document from the project. Deletion is always asynchronous.
The document is queued for deletion. All associated warehouse data, search
indexes, and graph nodes are removed asynchronously. Poll
/documents/indexing-status/ to confirm the document reaches deleted.
DELETE
/
projects
/
{project_id}
/
documents
/
{document_id}
/
Delete document
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text)const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request DELETE \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/documents/{document_id}/ \
--header 'Authorization: Bearer <token>'{
"error": "Authentication credentials were not provided."
}{
"error": "You do not have permission to perform this action."
}{
"error": "Not found."
}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
UUID of the project
UUID of the document
Response
Document deletion initiated