Update and Delete Published Rich Posts

Delete a Rich Post

A user can permanently delete their own Rich Post at any time. Deleting a post removes it along with all associated engagement data — including replies and reactions — from both the forum and the user's profile. No moderation is required for deletion.

Request

DELETE https://cf-blast.livelikecdn.com/api/v1/rich-posts/{rich_post_id}/

Example

curl -X DELETE "https://cf-blast.livelikecdn.com/api/v1/rich-posts/{rich_post_id}/" \
  --header "Authorization: Bearer {ACCESS_TOKEN}"

Response

A successful delete returns 204 No Content with an empty body.

❗️

Authorization is required!
A Rich Post can only be deleted by the user who created it. Always include the user's Access Token in the Authorization header.

Update a Published Rich Post

A user can update the text content of their own Rich Post within a configurable edit limit and time window after posting.

Rules & Constraints

Rich Post Object — Edit Tracking

Each Rich Post includes an edit_count field that tracks the total number of times the post has been updated.

This value can be used by your integration to enforce client-side edit limits or display edit history indicators in the UI.

📘

Backward Compatibility
The Max Edits Allowed (default: 9999) and Time Window (default: None) settings are both configurable at the application level. These defaults ensure backward compatibility for existing integrations. The edit_count field is always present on the Rich Post object and reflects the current number of edits made to the post.

Request

PATCH https://cf-blast.livelikecdn.com/api/v1/rich-posts/{rich_post_id}/

Request Body

{
  "title": "Updated post title",
  "content": "<p>Updated post content<br></p>",
  "localized_data": {
    "aa": {
      "title": "Localized title",
      "content": "Localized content"
    }
  }
}

Example

curl -X PATCH "https://cf-blast.livelikecdn.com/api/v1/rich-posts/{rich_post_id}/" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer {ACCESS_TOKEN}" \
  --data '{
    "title": "Updated post title",
    "content": "<p>Updated post content<br></p>",
    "localized_data": {
      "aa": {
        "title": "Localized title",
        "content": "Localized content"
      }
    }
  }'

Response

A successful edit returns 200 OK with the updated Rich Post object, including the incremented edit_count.

❗️

Authorization is required!
A Rich Post can only be edited by the user who created it, and only within the allowed time window and edit limit. Always include the user's Access Token in the Authorization header.

🚧

Edit window enforcement
Attempts to edit a post outside the allowed time window or after the edit limit has been reached will return an error response. Your integration should handle this gracefully in the UI by hiding the Edit option once the window has passed.