Producer editing and delivery
GuideAvailability varies by operation
These endpoints extend Producer generation with a song
library, editing, private downloads, and playlists or projects. Availability is
controlled per operation. A documented endpoint can return 503 until enabled;
this preview does not announce general availability. Existing generation routes
and their historical results remain supported.
Authenticate with
x-api-key. Reads require task:read; writes require task:create.
Choose an operation
Section titled “Choose an operation”- Edit lyrics, split stems, or trim — Create new resources from an authorized source.
- Export M4A or ZIP — Retrieve private downloads and understand retention.
- Manage songs and collections — Use revision-checked library and source changes.
Operations
Section titled “Operations”| Method and path | Result |
|---|---|
POST /api/v1/producer/lyrics/edit | Task containing newly edited lyrics |
POST /api/v1/producer/audio/stems | Task delivering vocals, drums, bass, and other |
POST /api/v1/producer/audio/trim | Task containing a new trimmed song |
POST /api/v1/producer/songs/{id}/exports | Task delivering one private M4A |
POST /api/v1/producer/exports/batches | Task delivering a ZIP of 1–20 M4A files and a manifest |
GET /api/v1/producer/songs | Authorized song library and continuation cursor |
GET /api/v1/producer/songs/{id} | Song metadata and current versions |
PATCH /api/v1/producer/songs/{id} | Local title change, or an explicitly requested shared-song change |
DELETE /api/v1/producer/songs/{id} | Remove your library entry, or explicitly request song deletion |
GET /api/v1/producer/collections, GET /api/v1/producer/collections/{id} | Platform playlists or projects |
POST /api/v1/producer/collections, PATCH /api/v1/producer/collections/{id} | Create or revise a collection |
Task-producing operations return the standard taskId, status, and
creditsRequired. Poll GET /api/v1/tasks/{taskId} or use the
Task stream and webhooks. Free library and collection
reads do not create generation tasks. Local library and collection writes do
not charge credits. For task prices, read the pricing catalog and the creation
receipt; do not derive a price from the HTTP method.
Resource access
Section titled “Resource access”Use a song returned by your own completed Task or authorized library. Library
id values are platform song IDs; older clip IDs remain accepted when associated
with your account. Lyrics references come from the selected text resource’s
metadata. A public URL or a known ID does not grant access. Unknown and
unauthorized references both return 404.
Authorization is checked again while work proceeds and when issuing download links. A removed library entry cannot be used for new downloads or edits. Some shared sources cannot be edited in place or combined in a single batch; split the request or use a permitted source if the operation is rejected.
Errors and recovery
Section titled “Errors and recovery”| Status | Action |
|---|---|
400 | Correct the fields, range, or unsupported format before a new request |
404 | Confirm that the source is still authorized for your account |
409 | Recover the original idempotent operation or reload its current version |
429 | Follow retry guidance and preserve the saved request key |
503 | The operation is unavailable; wait for availability before submitting |
If a request might already have created a Task, recover it using the same key and body instead of creating a second operation. Retry the same route: keys are scoped to the operation. The API does not expose arbitrary generation tools, template videos, Spaces, or unrestricted conversations through these routes.
Accepted operations continue recovery within their original delivery deadline. An uncertain submission can remain pending while its result is checked; keep polling the existing Task. Recovery preserves accepted work without submitting the same paid operation again. No new lyrics edit or rejected submission retry starts after the deadline or terminal settlement.
Explicit content-policy or generation failures and incomplete four-stem packages enter failure settlement without waiting for the deadline. Inspect the Task’s error and billing fields before deciding whether a new request is appropriate.