Create Bulk Actions

Submits a batch of up to 1000 create, update, and delete actions to be
processed asynchronously. Returns a background job status whose Show
endpoint reports aggregate progress and per-action results, including the
hashed IDs of created records.

Supported resource types are media, folder, subfolder, channel, and
channel_episode. A folder is a top-level folder (previously called a
project); a subfolder is nested inside one and requires folder_id and
name when created.

Deleting a folder or subfolder also soft-deletes its media. An account owner
or manager can restore that media from the trash until it purges. To keep the
media when deleting a subfolder, use the Delete Subfolder endpoint; it moves
the media to the folder's root level instead.

Each action in the batch is authorized and processed independently:
failures (including authorization failures) are reported per action and do
not prevent other actions from completing. Media creation is not supported
-- uploads and URL imports have their own endpoints.

Requires api token with one of the following permissions

Read, update & delete anything
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

A request containing an array of actions to process in bulk.

actions
array of objects
required
length between 1 and 1000

An array of actions to process. Maximum 1000 actions per request.
Each action specifies an operation (create, update, or delete),
a resource type, and the relevant payload or record ID.

actions*

A single action within a bulk request.

string
enum
required

The operation to perform. Media creation is not supported here --
uploads and URL imports have their own endpoints.

delete also soft-deletes media inside a folder or subfolder. An
account owner or manager can restore it from the trash until it purges.

Allowed:
string
enum
required

The type of resource to operate on. folder means a top-level folder
(previously called a project); use subfolder for a folder nested
inside one.

Allowed:
string

The hashed ID of the resource. Required for update and delete operations.

payload
object

The data for the operation. Required for create and update operations.
The accepted fields depend on the resource type and match the corresponding
create or update endpoint's request body (for example, a channel_episode
create takes the same fields as the Create Channel Episode endpoint,
including channel_id).

Creating a subfolder requires folder_id (the parent folder's hashed ID)
and name.

Headers
string
required
Defaults to 2026-07
Responses

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json