Media

Upload and manage the images and videos attached to posts, and the folders they are filed in.

📄️List media files

Returns a paginated list of the workspace's media, newest first (ordered by `created_at` descending, ties broken by `id` descending). The order is stable, so walking the pages never repeats or skips a file.

📄️Upload a media file (binary)

Uploads a single file in one `multipart/form-data` request. For files larger than your instance's chunked-upload threshold (`MIXPOST_CHUNKED_UPLOAD_THRESHOLD`, default 10 MB), use the chunked upload flow instead.

📄️Delete media files

Deletes one or more media records and detaches them from any post versions that reference them. Pass the media to delete as `items`, an array naming each file by its numeric id or by its uuid, at most 500 per request. Identifiers that resolve to nothing in this workspace are skipped silently, so `success: true` does not prove that anything was actually deleted.

📄️List media folders

Returns the workspace's whole folder tree in one response, ordered by name. Each folder names its parent by uuid, and reports how many files are filed at or below it.

📄️Create a media folder

Creates a folder, at the root or inside another. A workspace may nest folders five levels deep, counting a root folder as the first.

📄️Update a media folder

Renames a folder, moves it under another, or both. A folder cannot be moved into itself or into anything filed below it, and a move must leave room for the whole subtree within the five-level nesting cap.

📄️Delete a media folder

Deletes a folder. By default its contents are kept: the files it held, and any folders inside it, move up to where the deleted folder sat. Pass `delete_media` to remove the files as well.

📄️Get a media file

Get a media file

📄️Update a media file

Updates the media's `name`, `alt_text` and/or the folder it is filed in. Only the fields you include in the request body are changed; omitted fields are left untouched. A body naming none of them writes nothing and still succeeds.

📄️Initiate chunked upload

Step 1 of the chunked upload flow. Creates an upload session and returns the `upload_uuid` together with the chunk plan your client must follow (`chunk_size` and `total_chunks`).

📄️Upload a chunk

Step 2 of the chunked upload flow. Uploads a single chunk, identified by a zero-based `chunk_index` between `0` and `total_chunks - 1`. Chunks may be sent in any order — and in parallel — because they are reassembled in `chunk_index` order when the upload is completed.

📄️Complete chunked upload

Step 3 of the chunked upload flow. Reassembles the uploaded chunks into the final file, generates thumbnails and other conversions, creates the media record, and then discards the upload session. If any chunk is missing, assembly is aborted and no media record is created.