Skip to main content
GET
Get Upload Limits

Authorizations

Authorization
string
header
required

API key from Settings > Developer > REST API

Headers

Moda-Version
enum<string>
default:2026-05-01

Calendar-dated API version pin. New integrations should pin 2026-05-01 to opt into the newest response shapes. For back-compat the server also accepts requests with no header and resolves them to the current default (today: 2026-04-12); that default advances on each sunset date. Any unsupported value returns 400 unsupported_version.

Available options:
2026-04-12,
2026-05-01
Example:

"2026-05-01"

Response

Successful Response

Machine-readable upload size limits (GET /v1/uploads/limits).

Exists because the direct-lane ceiling is otherwise undiscoverable: the API gateway rejects an oversized POST /v1/uploads with a bare 413 that carries no error envelope, no limit, and no remedy. Static per deployment.

max_direct_upload_bytes
integer
required

Hard request-body ceiling for the multipart POST /v1/uploads lane (the API gateway's HTTP/1 cap; currently 32 MiB = 33,554,432 bytes). Requests above it are rejected with a bare, envelope-less 413 before reaching the app. Route larger files through the signed-URL flow (POST /v1/uploads/url + PUT + POST /v1/uploads/register); staying a margin below this number is wise since multipart framing counts toward it.

Example:

33554432

max_file_bytes
integer
required

Maximum stored file size on every upload lane (currently 250 MB, matching the in-app uploader). Enforced on actual bytes — at register time on the signed-URL flow — with a typed upload_too_large 413.

Example:

262144000