Sign in
content

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.

Grouping: bucketId files this piece with the post it was made from. A piece already grouped somewhere else is refused with a 409 rather than moved — ungroup it in the app first.

patch/v1/content/{contentId}

Path parameters

contentIdstring required

Unique identifier of the content

Request body

titlestring

New name for this piece in your library

bucketIdstring uuid

Group this piece with the post it was made from, so the writer sees them together in Content. Get the id from POST /v1/posts/{postId}/bucket. Omit for standalone work that isn't derived from anything.

Response

Content updated successfully

idstring required

Unique identifier for this piece of content

kindstring required

What this piece is: tweet, linkedin, newsletter, or x_article

titlestring required

What this piece is called in your library

excerptstring required

First readable line of the body, for listing views

status'draft' | 'published' | 'archived' required

Whether this piece has been delivered, is still a draft, or was archived

scheduledboolean required

Whether a scheduled send is queued against this piece

lockedReasonstring nullable required

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.

publishedAtstring nullable required

ISO 8601 timestamp of the first delivery, or null

urlstring nullable required

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.

archivedAtstring nullable required

ISO 8601 timestamp of when this piece was archived, or null

bucketIdstring nullable required

The bucket grouping this piece with the post it was made from, or null when it stands alone. Read it back with GET /v1/buckets/{bucketId}.

createdAtstring required

ISO 8601 timestamp of creation

updatedAtstring required

ISO 8601 timestamp of the last change

bodyobject required

The artifact itself, in the shape its kind uses

Changes