Skip to main content
GET
List supported upload formats

Authorizations

Authorization
string
header
required

Workspace credential issued from the automation console at /automation. Send it as Authorization: Bearer vq_ws_.... This is NOT a Data API key: a vq_key_ credential is refused here and names the other product in the error.

Response

Successful Response

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.

mediaTypes
string[]
required

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.

Example:
extensions
string[]
required

Every filename extension this API will accept, sorted and lowercase, each including its leading dot.

Example:
maxBytes
integer
required

Largest single file this API will open a session for. A larger sizeBytes is refused at initiate, before any URL is signed.

Example:

1

minPartSizeBytes
integer
required

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.

Example:

1

maxParts
integer
required

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.

Example:

1

Last modified on August 23, 2026