import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/available-document-metadata/"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/available-document-metadata/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/available-document-metadata/ \
--header 'Authorization: Bearer <token>'{
"tag": [
"Finance",
"Legal"
],
"source_path": [
"/path/to/document.pdf",
"/path/to/document.docx"
]
}{
"error": "Authentication credentials were not provided."
}{
"error": "You do not have permission to perform this action."
}{
"error": "Not found."
}List available document metadata
Retrieve all metadata keys and their distinct values across all active documents in the project.
This is useful for building filter UIs or understanding what metadata has been applied to documents.
Document metadata is user-entered (supplied at upload time or edited via the metadata endpoints), whereas document tags are LLM-inferred by tag extractors during pipeline runs.
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/available-document-metadata/"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/available-document-metadata/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/available-document-metadata/ \
--header 'Authorization: Bearer <token>'{
"tag": [
"Finance",
"Legal"
],
"source_path": [
"/path/to/document.pdf",
"/path/to/document.docx"
]
}{
"error": "Authentication credentials were not provided."
}{
"error": "You do not have permission to perform this action."
}{
"error": "Not found."
}Authorizations
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
Response
Successful response
Map of metadata keys to their distinct values (sorted).