Duplicate Release
Release
Duplicate Release
POST /releases//duplicate
POST
Duplicate Release
This endpoint requires authentication. Include your Bearer token in the Authorization header.
Description
Copies a release and its tracks into a newdraft owned by the caller.
Allowed from any status — duplicating a finished release as the basis for
the next one is the intended use.
The copy is fully independent:
- Workflow state (
submittedAt,reviewedAt,completedAt, auto-creation fields) is reset, andcreatedProductId/createdAssetIdsare cleared, so the copy never points at the original’s generated Product/Assets. - Track
isrcandiswcare NOT carried over — they are globally unique identifiers and duplicating them corrupts royalty attribution. The tenant’s auto-ISRC counter assigns on approval. - Track
assetIdis NOT carried over, so one catalogue Asset is never double-linked into two releases. metadatais copied wholesale EXCEPTmetadata.upcandmetadata.catalogNumber— the rest ofmetadata(includingddexMetadata) is preserved. Those two release-level identifiers are excluded for the same reason as trackisrc/iswc: they identify one release, not two, and are read by theupc-missingpre-delivery check, so copying them would let the duplicate clear that check using an identifier that belongs to the original.- Media objects are copied in cloud storage under the new release’s own path, so deleting media on the copy can never destroy the original’s files. A per-file copy failure omits that entry rather than failing the duplicate.
Copy of <title>, suffixed with a counter
(Copy of <title> (2)) when that name is already taken in the workspace.
Authorization:
- Required role:
useror higher (release owner, or admin+)