Skip to main content
PUT
This endpoint requires authentication. Include your Bearer token in the Authorization header.

Description

PUT /publishing-bootstrap/items/ Description: Records reviewer overrides on a PENDING staged item. finalData keys are strictly allowlisted (workTitle, iswc, languageCode, musicalWorkDistributionCategory, workType, duration, writers, resolveConflict, targetId) — any other key is rejected with 400. Ownership fields are NOT accepted. Share, territory, publisher, and agreement data (relativeShare, territories, prShare/mrShare/srShare, controlled, publisher/agreement references, and the like) are outside the vocabulary by design: the bootstrap is share-free end to end, and ownership is entered by a human after import through the regular publishing endpoints. finalData.writers, when present, REPLACES the proposal’s writer list entirely; each entry accepts only firstName, lastName, writerRole, ipiNameNumber, mbArtistId. targetId is only allowed together with resolveConflict: "link" and must reference a work in the caller’s workspace. Authorization:
  • Required role: admin or higher
Method: PUT

Code Examples

Authorizations

Authorization
string
header
required

JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"

Path Parameters

id
string<uuid>
required

Staged item id (itemId in the diff)

Body

application/json
finalData
object
required

Reviewer overrides, merged over any previous overrides. Keys are strictly ALLOWLISTED to the properties below — any other key is rejected with 400. Share, territory, publisher, and agreement fields are NOT accepted (e.g. relativeShare, territories, prShare/mrShare/srShare, controlled, publisherId): they are not in the vocabulary, so ownership data is structurally impossible to stage. writers entries are equally metadata-only.

Response

Item updated

status
string
Example:

"success"

message
string
Example:

"Publishing import item updated"

data
object