Create Folder
Creates a folder at the root or inside parent_id. Pass its folder_id to POST /v3/videos or POST /v3/video-translations to file output there. Names need not be unique, so store the ids you receive. Send an Idempotency-Key to make retries safe.
Authorizations
HeyGen API key. Obtain from your HeyGen dashboard.
Headers
Optional client-supplied key for safely retrying mutations. Subsequent calls within 24 hours that share this key replay the original response — even if the request body differs slightly (a warning is logged). A retry that arrives while the original is still in flight gets a 409 request_in_progress. Keys must be 1–255 characters from [A-Za-z0-9_:.-]; a UUID is a safe default. Scope is per-endpoint and per-resource: the same key on a different route or path parameter is independent.
1 - 255^[A-Za-z0-9_\-:.]{1,255}$Body
Request body for POST /v3/folders.
Folder name, 1-256 characters. Sibling folders may share a name.
1 - 256"Module 3 - Deploying to production"
ID of the folder to create this one in. Omit, pass null, or pass an empty string to create it at the workspace root. The parent must be a folder in the caller's workspace, of a kind this endpoint creates, that is not in the trash. Assets library folders are flat and cannot hold folders.
64"7c1f0b2e3d4a4f5e8a9b0c1d2e3f4a5b"
Kind of folder. 'mixed' is what the HeyGen web app's New folder action creates; 'video_translate' is what the Video Translate page creates. Folders the Assets library creates have kind 'asset'; they cannot be created or nested under here. Every kind is accepted as a folder_id destination on POST /v3/videos, POST /v3/video-translations and the other routes that take one, but the HeyGen app files only assets in an 'asset' folder, so a render placed in one may not appear in the Assets library view.
mixed, video, video_translate Response
Created.
A folder in the caller's workspace.

