Moderation

Approval queue, bulk actions, word filters, reports.

📄️Approve a pending comment

Marks a pending comment as published. Dual-auth: on the API-key path `moderator_id` (external user id) is required and resolves to the internal tenant user recorded on the moderation log; on the admin-JWT path the body field is ignored and the moderation log records `moderatorId: null` (admins are not tenant-scoped users). Both auth paths require the `moderate_content` capability.

📄️Reject a pending comment

Marks a pending comment as rejected. Same dual-auth semantics as approve — API-key callers must supply `moderator_id`, admin-JWT callers do not. Optional `reason` is persisted on the moderation log.

📄️List tenant word filters

Returns every blacklist/greylist word filter configured for the tenant. Dual-auth: mirrored under API-key and admin-JWT paths; both paths require `moderate_content`.

📄️Replace the full set of tenant word filters

Wholesale replace of the tenant word-filter list (up to 500 entries). Existing filters are removed. Dual-auth: mirrored under API-key and admin-JWT paths; both paths require `moderate_content`.

📄️List the tenant moderation audit log

Returns cursor-paginated moderation actions (approve/reject/auto_block/auto_pending) taken on tenant comments. Dual-auth: mirrored under API-key and admin-JWT paths; both paths require `moderate_content`.

📄️List pending comments awaiting moderation

Returns cursor-paginated comments in `pending` status. Dual-auth: mirrored under API-key and admin-JWT paths; both paths require `moderate_content`.