Reports

Discord has a reporting system that allows users to report messages or profiles that violate Discord's Terms of Service or Community Guidelines. When a user creates a report, it is sent to Discord's Trust and Safety team for review. The team evaluates the report and takes appropriate action, which may include warning the user, temporarily suspending their account, or permanently banning them from the platform.

There are multiple versions of the reporting API:

• V1: The original version of the reporting API, also known as dirt. Supports reporting messages and users.
• V2: An updated version of the original reporting API that includes detailed report types and saves a snapshot of the reported message for review. Supports reporting messages only.
• V3: The latest version of the reporting API, known as in-app reports, that includes additional report types and improved functionality. Supports reporting messages, users, guilds, scheduled events, and more.
• DSA: A special version of reports V3 that can be used by users living in the European Union to comply with the Digital Services Act.

Considerations

When using the reporting API, keep the following in mind:

• Only resources you have access to can be reported. For example, you cannot report a message in a private channel you cannot access.
• You must have a verified email on your account to create reports.
• You cannot report your own messages or profile.
• Reports are anonymous. The user being reported will not be notified of who reported them.
• Abuse of the reporting system may result in action being taken against your account.

Reports V1

The original version of the reporting API, also known as "dirt". Supports reporting messages and users.

Endpoints

Returns a list of report reason objects that can be used when creating a report for a message or user.

Query String Params

Either channel_id and message_id, or user_id must be provided.

Report Reason Structure

Example Report Reason

{
  "reason": 2,
  "label": "Spam or Phishing Links",
  "description": "Fake links, invites to a server via bot, malicious links or attachments."
}

Creates a report for a message or user.

JSON Params

¹ Either channel_id and message_id, or user_id must be provided.

Response Body

Reports V2

An updated version of the original reporting API that includes detailed report types and saves a snapshot of the reported message for review. Supports reporting messages only.

Endpoints

Returns a list of report option objects that can be used when creating a report for a message.

Report Option Structure

Report Option Sub-Type Structure

Example Report Option

{
  "value": "spamming",
  "label": "Spamming",
  "description": "Unsolicited advertisements",
  "sub_question": "How is this spam?",
  "sub_types": [
    {
      "value": "sub_spam",
      "label": "User is sending spam messages or requests"
    },
    {
      "value": "sub_spambot",
      "label": "This is a spambot account"
    }
  ]
}

Stages a report for a message, returning a token that can be used to create the report containing the serialized message data.

Response Body

Creates a report for a message, including a snapshot of the message for review. Requires the MANAGE_MESSAGES permission if the channel is in a guild. Returns a 204 empty response on success.

JSON Params

Reports V3

The latest version of the reporting API, known as "in-app reports", that includes additional report types and improved functionality. Supports reporting messages, users, guilds, scheduled events, and more.

DSA

A special version of reports V3 that can be used by users living in the European Union to comply with the Digital Services Act. Unlike regular reports, DSA reports do not require an account to submit. Instead, users simply need to verify an email address. Additionally, instead of the standard report menu types, DSA reporters fetch their allowed report types from a separate endpoint.

Note that the unauthenticated reporting endpoints require that either authentication or a fingerprint is provided for experiment tracking purposes.

Report Menu Object

Report Menu Structure

Report Node Structure

¹ Node IDs are unique across all report menu types and often reused in multiple menus.

Report Button Structure

Report Button Type

Report Node Child Structure

This object is represented as an array of the following fields:

Report Element Structure

Report Element Type

¹ Nested array is in the format (name, label, description?).

Dropdown Element Structure

Dropdown Option Structure

Free Text Element Structure

Text Line Resource Element Structure

Text Resource Element Structure

External Link Element Structure

Report Menu Type

Example Report Menu

{
  "name": "user",
  "variant": "3",
  "version": "1.0",
  "postback_url": "/api/reporting/user",
  "root_node_id": 1,
  "success_node_id": 1,
  "fail_node_id": 1,
  "nodes": {
    "1": {
      "id": 1,
      "key": "GENERIC_SUBMIT",
      "header": "Report Summary",
      "subheader": "Review your report before submitting.",
      "info": null,
      "button": {
        "type": "submit",
        "target": null
      },
      "elements": [
        {
          "name": "breadcrumbs",
          "type": "breadcrumbs",
          "data": null,
          "should_submit_data": false,
          "skip_if_unlocalized": false,
          "is_localized": true
        }
      ],
      "report_type": null,
      "children": [],
      "is_multi_select_required": false,
      "is_auto_submit": false
    }
  }
}

Endpoints

Returns a report menu object for the specified type. The menu contains a hierarchical tree of nodes that guide users through the reporting process, including questions, options, and submission steps.

Query String Params

Submits a completed report based on the user's navigation through a report menu. This endpoint processes the collected information from the menu flow and creates a formal report for review by Discord's Trust and Safety team.

JSON Params

Response Body

Queries whether the user can use unauthenticated reporting. Returns an empty object on success.

Returns the report menu types available for unauthenticated reporting.

Response Body

Sends a verification code to the user's email address to initiate the unauthenticated reporting process for the specified type (must be one of the types returned by Get Unauthenticated Report Capabilities). Returns an empty object on success.

JSON Params

Verifies the email code sent to the user to confirm their email address for unauthenticated reporting for the specified type (must be one of the types returned by Get Unauthenticated Report Capabilities).

JSON Params

Response Body

Returns a report menu object for the specified type (must be one of the types returned by Get Unauthenticated Report Capabilities). The menu contains a hierarchical tree of nodes that guide users through the reporting process, including questions, options, and submission steps.

Query String Params

Submits a completed unauthenticated report based on the user's navigation through a report menu. This endpoint processes the collected information from the menu flow and creates a formal report for review by Discord's Trust and Safety team.

JSON Params

Submits a request to have a report on your account reviewed. Report review links are present in emails sent informing you of actions taken on your account. When clicked, these links redirect to https://discord.com/report-review?token=..., where the token can be used with this endpoint to request a review. Returns an empty object on success.

JSON Params