#Event Reports API

Manage reports of policy-violating content submitted by users.

#List Event Reports

List all event reports with pagination and filtering.

Endpoint: GET /_synapse/admin/v1/event_reports

Query Parameters:

Example Request:

curl -X GET "https://your-server/_synapse/admin/v1/event_reports?limit=20&dir=b" \
  -H "Authorization: Bearer <access_token>"

Example Response:

{
  "event_reports": [
    {
      "id": 12,
      "received_ts": 1609459200000,
      "room_id": "!roomid:example.com",
      "event_id": "$eventid:example.com",
      "user_id": "@reporter:example.com",
      "reason": "Spam content",
      "score": -100,
      "sender": "@spammer:example.com",
      "canonical_alias": "#general:example.com",
      "name": "General Chat"
    }
  ],
  "total": 1,
  "next_token": null
}

#Get Event Report Details

Get detailed information about a specific event report, including the reported event content.

Endpoint: GET /_synapse/admin/v1/event_reports/{report_id}

Path Parameters:

• report_id - Numeric report identifier

Example Request:

curl -X GET "https://your-server/_synapse/admin/v1/event_reports/12" \
  -H "Authorization: Bearer <access_token>"

Example Response:

{
  "id": 12,
  "received_ts": 1609459200000,
  "room_id": "!roomid:example.com",
  "event_id": "$eventid:example.com",
  "user_id": "@reporter:example.com",
  "reason": "Spam content",
  "score": -100,
  "event_json": {
    "type": "m.room.message",
    "content": {
      "msgtype": "m.text",
      "body": "Buy cheap products at spam-site.example!"
    },
    "sender": "@spammer:example.com",
    "origin_server_ts": 1609458000000,
    "event_id": "$eventid:example.com"
  }
}

#Delete Event Report

Delete an event report after it has been handled.

Endpoint: DELETE /_synapse/admin/v1/event_reports/{report_id}

Example Request:

curl -X DELETE "https://your-server/_synapse/admin/v1/event_reports/12" \
  -H "Authorization: Bearer <access_token>"

Response: 200 OK with empty body on success.

#Event Report Fields Reference

#Handling Reports Workflow

1. Review new reports - List reports with dir=b to see most recent first.

2. Investigate - Get report details to see the full event content.

3. Take action - Based on severity, you may:

   • Warn the sender
   • Redact the event
   • Shadow ban the user
   • Deactivate the user account
   • Ban the room

4. Clean up - Delete the report after handling.

#Example: Moderate Reported Content

# 1. List recent reports
curl -X GET "https://your-server/_synapse/admin/v1/event_reports?limit=10" \
  -H "Authorization: Bearer <access_token>"

# 2. Get details of report #12
curl -X GET "https://your-server/_synapse/admin/v1/event_reports/12" \
  -H "Authorization: Bearer <access_token>"

# 3. If spam, shadow ban the sender
curl -X POST "https://your-server/_synapse/admin/v1/users/@spammer:example.com/shadow_ban" \
  -H "Authorization: Bearer <access_token>"

# 4. Delete the handled report
curl -X DELETE "https://your-server/_synapse/admin/v1/event_reports/12" \
  -H "Authorization: Bearer <access_token>"