Edit a piece of content
Rename a piece of content, replace its body, or both.
Replacement, not a merge: body replaces the artifact entirely, in the same shape the kind takes on create. Send the whole thing, not just the part that changed. Media already attached to the draft is the one exception — you can’t send it back, so it’s carried over rather than dropped.
Scheduled pieces are locked: if a send is queued or already running for this piece, its words go out exactly as written, so an edit to body is refused with an explanation. Cancel the schedule in the app first. Renaming is always allowed — a title isn’t published anywhere.
Authorizations
API key for authenticating protected endpoints. Pass as Bearer token in Authorization header.
Path Parameters
Unique identifier of the content
Body
Body
Response
Content updated successfully
Unique identifier for this piece of content
What this piece is: tweet, linkedin, newsletter, or x_article
What this piece is called in your library
First readable line of the body, for listing views
Whether this piece has been delivered, is still a draft, or was archived
draft, published, archived Whether a scheduled send is queued against this piece
Why this piece can't be edited right now, or null when it can. A queued or in-flight send locks the words, because they go out exactly as written.
ISO 8601 timestamp of the first delivery, or null
Where this piece went live, from the same delivery publishedAt came from. Null when it hasn't been delivered, and null by design for a channel that publishes no page: a custom email renders into the message itself, so there is no address to link to. Never guessed — a delivery whose id isn't shaped like its channel reports null rather than a link that would 404.
ISO 8601 timestamp of when this piece was archived, or null
ISO 8601 timestamp of creation
ISO 8601 timestamp of the last change
The artifact itself, in the shape its kind uses

