Sign in
Redactions

Redact Content in a Confluence Blog Post

Redacts sensitive content in a Confluence blog post by replacing specified text ranges with redaction markers. Each redaction in the response includes a unique UUID for restoration (except code block redactions). The response metadata items maintain the same order as the input redaction pointers, and completely overlapping redactions are merged into a single redaction with one UUID.

Note: This endpoint requires Atlassian Guard Premium.

post/blogposts/{id}/redact

Path parameters

idinteger required

The ID of the blog post to redact content from.

Request body

createdAtstring date-time required

Timestamp when the content was last updated.

cleanHistoryboolean nullable

Whether to clean up previous versions containing the redaction. When true, historical versions of the content that contain the redacted text will be squashed.

versionNumberinteger nullable

Optional version number of the content to redact. When specified, the redaction will target a specific historical version of the content rather than the current version.

  • If omitted or null, the redaction applies to the current (latest) version of the content.
  • When provided, must be a valid version number that exists for the content.

Note: Version numbers start at 1 and increment with each content update.

Response

Redaction Accepted. The response contains details about the redactions that were applied.

Changes

No recorded changes to this endpoint across all 2 revisions of this API.