For most use cases, the
slideless CLI handles the upload flow end-to-end. This reference is for custom tooling.Endpoint
Auth
Required scope:
presentations:write.
Multipart fields
Order-independent. Send all five in one request:Hash verification
The backend recomputes the SHA-256 of the received bytes and compares against the declaredsha256. If they don’t match, the blob is deleted and the call returns 400 hash-mismatch. This prevents a malicious client from smuggling corrupt content into another user’s namespace.
Response (200)
size: 0 indicates the blob was already present — upload was skipped (idempotent).
Plan caps
The per-file cap depends on your plan:
Uploads over the cap fail with
413 payload-too-large.
Example
curl
Node.js (native FormData + Blob)
Errors
Next
- POST /commitPresentationVersion — after all missing blobs are uploaded, commit the manifest.