What this API will accept, and how it will cut it into parts. Derived from `adapters/upload_media`, which is itself derived from `app.core.file_validation`, rather than from the web app's `get_supported_formats()`. That catalogue carries categories and security risk levels and INCLUDES macro-enabled formats the upload path refuses, so publishing it would tell a caller a `.docm` is supported and then answer 415 when they sent one. `supportedMediaTypes` here is the same list `unsupported-media-type` carries in its problem document, from the same constant. A test asserts the two are equal, because the day they drift the error becomes the more accurate one and this endpoint becomes the lie.
Every IANA media type this API will accept for an upload, sorted. Compare case-insensitively: media types are case-insensitive per RFC 2045, and this API folds both sides.
extensions
array
Every filename extension this API will accept, sorted and lowercase, each including its leading dot.
maxBytes
integer
Largest single file this API will open a session for. A larger `sizeBytes` is refused at initiate, before any URL is signed.
minPartSizeBytes
integer
The floor storage applies to every part EXCEPT the last. A one-part upload of any size is legal, which is why a small file is not a separate code path.
maxParts
integer
Most parts a single upload may be cut into. The part size is chosen server-side from the file size and returned on the session.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/vaquill-ai/json-schema/vaquill-ai-upload-formats-schema.json",
"title": "UploadFormats",
"description": "What this API will accept, and how it will cut it into parts.\n\nDerived from `adapters/upload_media`, which is itself derived from\n`app.core.file_validation`, rather than from the web app's\n`get_supported_formats()`. That catalogue carries categories and security\nrisk levels and INCLUDES macro-enabled formats the upload path refuses, so\npublishing it would tell a caller a `.docm` is supported and then answer 415\nwhen they sent one.\n\n`supportedMediaTypes` here is the same list `unsupported-media-type` carries\nin its problem document, from the same constant. A test asserts the two are\nequal, because the day they drift the error becomes the more accurate one\nand this endpoint becomes the lie.",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/vaquill-ai-uploads-api-openapi.yml#/components/schemas/UploadFormats",
"properties": {
"mediaTypes": {
"items": {
"type": "string"
},
"type": "array",
"title": "Mediatypes",
"description": "Every IANA media type this API will accept for an upload, sorted. Compare case-insensitively: media types are case-insensitive per RFC 2045, and this API folds both sides."
},
"extensions": {
"items": {
"type": "string"
},
"type": "array",
"title": "Extensions",
"description": "Every filename extension this API will accept, sorted and lowercase, each including its leading dot."
},
"maxBytes": {
"type": "integer",
"title": "Maxbytes",
"description": "Largest single file this API will open a session for. A larger `sizeBytes` is refused at initiate, before any URL is signed."
},
"minPartSizeBytes": {
"type": "integer",
"title": "Minpartsizebytes",
"description": "The floor storage applies to every part EXCEPT the last. A one-part upload of any size is legal, which is why a small file is not a separate code path."
},
"maxParts": {
"type": "integer",
"title": "Maxparts",
"description": "Most parts a single upload may be cut into. The part size is chosen server-side from the file size and returned on the session."
}
},
"additionalProperties": false,
"type": "object",
"required": [
"mediaTypes",
"extensions",
"maxBytes",
"minPartSizeBytes",
"maxParts"
]
}
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.