curl --request GET \
--url https://{host}/v2/workspaces/slug:storage/webhooks/v1/supported_formatsconst options = {method: 'GET'};
fetch('https://{host}/v2/workspaces/slug:storage/webhooks/v1/supported_formats', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://{host}/v2/workspaces/slug:storage/webhooks/v1/supported_formats"
response = requests.get(url)
print(response.text){
"object": "list",
"data": [
{
"mime": "message/rfc822",
"extensions": [
"eml"
],
"family": "document"
}
],
"mime_types": [
"<string>"
],
"extensions": [
"<string>"
],
"extension_mime_types": {
"eml": "message/rfc822",
"msg": "application/vnd.ms-outlook"
},
"resolved_mime": "message/rfc822",
"ingestible": true
}List the file formats a knowledge base can ingest
The single catalog of ingestible formats, the list the upload picker offers, connector syncs follow and the ingestion check applies. Static and identical for every caller, so no authentication is required. Families: document, text, data, email, calendar, image, audio, video; image, audio and video files are parsed by a language model. Given mime_type and/or filename, the response also carries the ingestion check’s verdict for that one file (resolved_mime, ingestible).
curl --request GET \
--url https://{host}/v2/workspaces/slug:storage/webhooks/v1/supported_formatsconst options = {method: 'GET'};
fetch('https://{host}/v2/workspaces/slug:storage/webhooks/v1/supported_formats', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://{host}/v2/workspaces/slug:storage/webhooks/v1/supported_formats"
response = requests.get(url)
print(response.text){
"object": "list",
"data": [
{
"mime": "message/rfc822",
"extensions": [
"eml"
],
"family": "document"
}
],
"mime_types": [
"<string>"
],
"extensions": [
"<string>"
],
"extension_mime_types": {
"eml": "message/rfc822",
"msg": "application/vnd.ms-outlook"
},
"resolved_mime": "message/rfc822",
"ingestible": true
}Query Parameters
Declared type of one file to check. Parameters (; charset=...) are ignored.
256Name of that file. Its extension types the file when mime_type is missing or octet-stream (application/ or binary/); an extension nothing here parses resolves to application/octet-stream, which is not ingestible.
512Response
Supported formats.
list Only with mime_type or filename. The type the ingestion check applies - the declared one, or the extension's when the declared one is missing or octet-stream (application/ or binary/). Empty when the file has neither a type nor an extension (such a file is ingestible).
"message/rfc822"
Only with mime_type or filename. False when the ingestion check would refuse the file (UNSUPPORTED_FILE_TYPE).
Was this page helpful?