import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/connections/{connection_id}/set-file-type-rules/"
payload = { "extensions": ["<string>"] }
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({extensions: ['<string>']})
};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/connections/{connection_id}/set-file-type-rules/', 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}/connections/{connection_id}/set-file-type-rules/ \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"extensions": [
"<string>"
]
}
'Set the file-type allow/deny rules for a connection
Stores the connection’s file-type rules (any provider). Rules gate creation of NEW
documents from the next sync: allow imports only the listed extensions, deny
imports everything except them. Already-imported documents keep receiving updates
and delete-propagation regardless of rules. File types the platform can’t parse
(audio/video, .xml, .url, …) are always skipped (platform baseline, independent of
these rules). New connections are created with an allow rule for document types. Extensions are normalized
(lowercased, leading dots stripped, deduplicated). Only the connection owner may
call this.
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/connections/{connection_id}/set-file-type-rules/"
payload = { "extensions": ["<string>"] }
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({extensions: ['<string>']})
};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/connections/{connection_id}/set-file-type-rules/', 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}/connections/{connection_id}/set-file-type-rules/ \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"extensions": [
"<string>"
]
}
'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
UUID of the connection
Body
Response
Updated connection (rules stored under params.file_type_rules)