Skip to content

Remove an asset from a post

DELETE
/posts/{id}/assets/{asset_id}

Removes an asset from a post’s members. The asset itself isn’t changed.

You need to be signed in and allowed to edit the post: you’re its author, you hold posts.admin or system.admin, or you hold posts.admin for the post’s team. A post that doesn’t exist or is deleted answers 404, and anyone else gets 403. You don’t need to be able to read the asset.

The answer is 204 whether or not the asset was a member, so removing it twice, or naming an asset that doesn’t exist, also gets 204. A post can be left with no members. An asset that is also the post’s cover stays its cover.

The post’s updated_at doesn’t change, and nothing is recorded as an activity. Removing an actual member makes the server work out the post’s mature rating, AI label and search text again, and an asset that stays the post’s cover still counts toward the first two. Each server’s cached copy of the post is dropped on a best-effort basis either way.

id
required
string format: uuid

The post’s id.

asset_id
required
string format: uuid

The asset to remove.

The asset isn’t a member of the post now.

Authentication required, missing, or invalid

object
error
required

Human-readable error summary

string
Example
the request could not be completed
Example
{
"error": "authentication required: sign in and retry with a valid session or API token"
}

Authenticated but missing required capabilities

object
error
required

Human-readable error summary

string
Example
the request could not be completed

Resource not found

object
error
required

Human-readable error summary

string
Example
the request could not be completed