Delete document tag extractor
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/document-tag-extractors/{extractor_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}/document-tag-extractors/{extractor_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}/document-tag-extractors/{extractor_id}/ \
--header 'Authorization: Bearer <token>'{
"error": "Authentication credentials were not provided."
}{
"error": "You do not have permission to perform this action."
}{
"error": "Not found."
}Document Tag Extractors
Delete document tag extractor
Delete the DocumentTagExtractor. The related
extracted_document_tags_table is cleaned up on cascade.
DELETE
/
projects
/
{project_id}
/
document-tag-extractors
/
{extractor_id}
/
Delete document tag extractor
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/document-tag-extractors/{extractor_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}/document-tag-extractors/{extractor_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}/document-tag-extractors/{extractor_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 extractor
Response
Deleted