Overview - Uploads APIs
Finished uploads (POST /upload, upload-from-url, or complete-multipart) return `id` and `filePath` — map to `media[].id` and `media[].path` on POST /public/posts.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Endpoints
How uploads chain into posts
Upload an asset first. The API returns data.id and data.filePath. Pass them as media: [{ id, path }] inside the POST /public/posts body — path is the post field and must be the upload filePath.
Hosted inbound body limit
POST /public/upload on OpenQuok Cloud is capped at about 4.5 MB by the function gateway (HTTP 413). The application video cap is still 1 GB. For larger files use the multipart endpoints below, or call openquok upload / OpenQuok.upload() — both switch automatically. Do not compress a TikTok or Reels clip to 3.5 MB just to squeeze through the simple upload.
Constraints
| Constraint | Value |
|---|---|
| Multipart field name | file |
| Allowed mime types | image/, video/, audio/*, application/pdf |
| Simple upload (hosted) | About 4 MB inbound (leave headroom under the 4.5 MB gateway) |
| Multipart part size | 5 MiB minimum except the last part |
| Per-file size cap | MAX_MEDIA_VIDEO_UPLOAD_BYTES (1 GB for video; shared with the session uploader) |
| Auth header | Authorization: Bearer opo_... (workspace programmatic token or third-party OAuth app token) |