Skip to main content
Use comment update APIs when a user edits a comment or replaces its image attachments. The SDK sends the update to the server; permission, ownership, and moderation rules are enforced by the backend and surfaced as SDK errors.

Update Fields

Upload image files first, then pass the uploaded file IDs to the update API. Passing local file paths to comment update is not supported.

Parameters

Update Text

Update text and other editable fields by loading the comment ID and applying the platform-specific update call.

Update Image Attachments

Set the attachment list to the full list you want the comment to keep. To preserve an existing image, include its uploaded file ID in the update payload.

Clear Optional Fields

Different SDKs distinguish between “leave this field unchanged” and “replace this field with an empty value.”

Notes

  • For TypeScript image attachment updates, build the attachment payload using the same uploaded-file shape as comment creation.
  • For iOS, Android, and Flutter, nil / unset attachment fields leave existing attachments unchanged; an explicit empty list removes attachments.
  • Rebuild mention and link payloads from the edited text before updating a comment.
  • Handle permission, not-found, and moderation errors from the SDK call rather than relying only on client-side checks.

Delete Comment

Soft delete or permanently delete comments where supported.

Query Comments

Query comments and include deleted comments when needed.

Image Comment

Upload images before attaching them to comments.

Text Comment

Create top-level comments and replies.