Resolve Reports

Overview

Close a pending moderation report by id - either delete the reported message (message_deleted) or dismiss the report without deleting content (dismissed).

On success, the API returns the updated report with status, resolution, resolutionNote, and resolvedAt filled in so the Platform queue can move the row out of pending.

When to use this endpoint?

Use Resolve Reports when:

A moderator confirms a violation and wants the message removed (message_deleted).
A report is invalid or already handled and should be closed without deleting the message (dismissed).
You need to attach an optional note explaining the decision for audit / queue history.
Clearing a pending item after reviewing it from List Reports.

Part of the client Platform Moderation module. Get reportId from List Reports (data.list[]._id). Mute or ban the sender separately via Mute / Ban endpoints.

Request Fields

Field	Required	Description
resolution	Required	How to close the report. Allowed values: `message_deleted` (delete the message; report `status` becomes `resolved`) or `dismissed` (keep the message; report `status` becomes `dismissed`).
note	Optional	Moderator note stored as `resolutionNote` on the report.

PATCH{baseUrl}/api/{apiVersion}/client/moderation/reports/:reportId/resolve

Authentication: Required (Bearer token)
Tenant-scoped: Yes (tenant DB - requires x-client-id)

Request Headers

Header	Value	Description
Authorization	Bearer <access_token>	Client Access Token with tenant admin privileges (Platform panel).
Content-Type	application/json	Required when sending a JSON body.
is-tenant	true	Targets the tenant DB ("true", needs x-client-id).
x-client-id	{{clientId}}	Tenant (client) id. Required when is-tenant=true.

Path Parameters

Parameter	Example	Description
reportId	6a589bb7cfa34ab66e35b2b3	The report's `_id` from List Reports.

Request Payload

Delete the message (`message_deleted`)

Use when the report is valid and the content should be removed. Report status becomes resolved.

json

1{2  "resolution": "message_deleted",3  "note": "Violates content policy"4}

Dismiss the report (`dismissed`)

Use when no action on the message is needed. Report status becomes dismissed.

json

1{2  "resolution": "dismissed",3  "note": "Not a policy violation after review"4}

Success Response (HTTP 200 OK)

Returns the updated report document. In this example resolution is message_deleted, so status is resolved and resolutionNote mirrors the request note. Nested list enrichments (message, messageSender) are not required on this response.

json

1{2  "success": true,3  "message": "Report resolved successfully",4  "data": {5    "_id": "6a589bb7cfa34ab66e35b2b3",6    "messageId": "6a589b97d379191dcf5fadbb",7    "conversationId": "6a589b96cfa34ab66e35b2ac",8    "reportedBy": "6a589b96cfa34ab66e35b2aa",9    "reason": "Offensive language",10    "status": "resolved",11    "resolution": "message_deleted",12    "resolutionNote": "Violates content policy",13    "resolvedAt": "2026-07-16T08:52:07.173Z",14    "createdAt": "2026-07-16T08:52:07.003Z",15    "updatedAt": "2026-07-16T08:52:07.173Z"16  },17  "error": null18}

Common Errors

Resolve fails when auth is invalid, the report id is missing, or the body is invalid.

HTTP 401 Unauthorized - No token

json

1{2  "success": false,3  "message": "No token, authorization denied",4  "data": null,5  "error": "Unauthorized"6}

HTTP 403 Forbidden - Tenant admin required

json

1{2  "success": false,3  "message": "Access denied: tenant admin privileges required",4  "data": null,5  "error": null6}

HTTP 404 Not Found - Report missing

json

1{2  "success": false,3  "message": "Entity not found",4  "data": null,5  "error": "Entity not found"6}

Code	Reason
400 Bad Request	Missing `resolution`, or value is not `message_deleted` / `dismissed`.
401 Unauthorized	Access Token is missing, invalid, or expired.
403 Forbidden	Tenant admin privileges required for Platform Moderation.
404 Not Found	No report exists for the given `reportId`.
500 Internal Server Error	An unexpected error occurred while resolving the report.

Best Practices

Only resolve reports that are still pending in the queue UI.
Prefer message_deleted for clear policy violations; use dismissed when content should remain visible.
Always send a short note so audit history explains the decision.
After resolve, refetch List Reports so the inbox status filters update.
Mute or ban the sender as a separate step when the violation warrants account action.

Report closed

Update the queue from the returned status / resolution, then use Mute/Unmute User or Ban/Unban User if the sender needs further action.

Overview

Close a pending moderation report by id - either delete the reported message (message_deleted) or dismiss the report without deleting content (dismissed).

On success, the API returns the updated report with status, resolution, resolutionNote, and resolvedAt filled in so the Platform queue can move the row out of pending.

When to use this endpoint?

Use Resolve Reports when:

A moderator confirms a violation and wants the message removed (message_deleted).
A report is invalid or already handled and should be closed without deleting the message (dismissed).
You need to attach an optional note explaining the decision for audit / queue history.
Clearing a pending item after reviewing it from List Reports.

Part of the client Platform Moderation module. Get reportId from List Reports (data.list[]._id). Mute or ban the sender separately via Mute / Ban endpoints.

Field

Required

Description

resolution

Required

How to close the report. Allowed values: message_deleted (delete the message; report status becomes resolved) or dismissed (keep the message; report status becomes dismissed).

note

Optional

Moderator note stored as resolutionNote on the report.

Request Headers

Header	Value	Description
Authorization	Bearer <access_token>	Client Access Token with tenant admin privileges (Platform panel).
Content-Type	application/json	Required when sending a JSON body.
is-tenant	true	Targets the tenant DB ("true", needs x-client-id).
x-client-id	{{clientId}}	Tenant (client) id. Required when is-tenant=true.

Parameter

Example

Description

reportId

6a589bb7cfa34ab66e35b2b3

The report's _id from List Reports.

Request Payload

Delete the message (`message_deleted`)

Use when the report is valid and the content should be removed. Report status becomes resolved.

json

1{2  "resolution": "message_deleted",3  "note": "Violates content policy"4}

Dismiss the report (`dismissed`)

Use when no action on the message is needed. Report status becomes dismissed.

json

1{2  "resolution": "dismissed",3  "note": "Not a policy violation after review"4}

Success Response (HTTP 200 OK)

json

1{2  "success": true,3  "message": "Report resolved successfully",4  "data": {5    "_id": "6a589bb7cfa34ab66e35b2b3",6    "messageId": "6a589b97d379191dcf5fadbb",7    "conversationId": "6a589b96cfa34ab66e35b2ac",8    "reportedBy": "6a589b96cfa34ab66e35b2aa",9    "reason": "Offensive language",10    "status": "resolved",11    "resolution": "message_deleted",12    "resolutionNote": "Violates content policy",13    "resolvedAt": "2026-07-16T08:52:07.173Z",14    "createdAt": "2026-07-16T08:52:07.003Z",15    "updatedAt": "2026-07-16T08:52:07.173Z"16  },17  "error": null18}

Common Errors

Resolve fails when auth is invalid, the report id is missing, or the body is invalid.

HTTP 401 Unauthorized - No token

json

1{2  "success": false,3  "message": "No token, authorization denied",4  "data": null,5  "error": "Unauthorized"6}

HTTP 403 Forbidden - Tenant admin required

json

1{2  "success": false,3  "message": "Access denied: tenant admin privileges required",4  "data": null,5  "error": null6}

HTTP 404 Not Found - Report missing

json

1{2  "success": false,3  "message": "Entity not found",4  "data": null,5  "error": "Entity not found"6}

Code	Reason
400 Bad Request	Missing `resolution`, or value is not `message_deleted` / `dismissed`.
401 Unauthorized	Access Token is missing, invalid, or expired.
403 Forbidden	Tenant admin privileges required for Platform Moderation.
404 Not Found	No report exists for the given `reportId`.
500 Internal Server Error	An unexpected error occurred while resolving the report.

Best Practices

Only resolve reports that are still pending in the queue UI.
Prefer message_deleted for clear policy violations; use dismissed when content should remain visible.
Always send a short note so audit history explains the decision.
After resolve, refetch List Reports so the inbox status filters update.
Mute or ban the sender as a separate step when the violation warrants account action.

Delete the message (message_deleted)

Dismiss the report (dismissed)

HTTP 401 Unauthorized - No token

HTTP 403 Forbidden - Tenant admin required

HTTP 404 Not Found - Report missing

Report closed

Delete the message (message_deleted)

Dismiss the report (dismissed)

HTTP 401 Unauthorized - No token

HTTP 403 Forbidden - Tenant admin required

HTTP 404 Not Found - Report missing

Report closed

Delete the message (`message_deleted`)

Dismiss the report (`dismissed`)

Delete the message (`message_deleted`)

Dismiss the report (`dismissed`)