A free and open source instant messaging and VoIP chat app built for friends, groups, and communities.
---
# SPDX-License-Identifier: AGPL-3.0-or-later
title: Reports
description: Report flows, report submission, the reason catalog and Digital Services Act notices.
---
import RouteHeader from '@/components/RouteHeader.astro';
A report tells the instance's moderators that a message, a user profile or a guild breaks the rules. A signed-in user reports a message, a profile or a guild by answering a [report flow](#report-flows), and anyone with a verified email address can file a Digital Services Act notice without an account. Moderators work with stored reports through the [Admin Reports API](/admin-api/reports/).
A Digital Services Act notice takes three calls, [Send DSA report email](#send-dsa-report-email), [Verify DSA report email](#verify-dsa-report-email) and [Create DSA report](#create-dsa-report), and the reporter gets a receipt email with the report ID when the notice is filed.
Fluxer keeps a copy of the reported content and profile when a report is filed, and editing or deleting the content afterwards doesn't change it.
## Report flows
A report flow is the set of screens a reporter answers before a report is filed. [Get report flow](#get-report-flow) returns every screen of one flow, already translated, and a client renders the flow from that response.
| Screen kind | Field that is set | What the reporter does |
| --- | --- | --- |
| Choice | `options` | Picks one option |
| Checklist | `checklist` | Ticks at least `min_checked` items and continues |
| Info | `next_screen_id` | Reads the text and continues |
The reporter starts at `start_screen_id` and follows each [outcome](#report-flow-outcome-object) until one has the type `submit`, and this path is the walk. Each screen on the walk adds one [step](#report-flow-step-object) to the submission, and the report is filed under the `reason` of the final `submit` outcome. An `end` outcome finishes the walk without a report.
### Revision hash
`revision_hash` identifies the structure of one flow variant and changes whenever a screen, option, item or outcome changes. A submission sends back the hash of the flow the reporter answered.
| Walk | Hash | Result |
| --- | --- | --- |
| Valid | Current or outdated | The report is filed |
| Invalid | Current | 400 `INVALID_REPORT_FLOW_ANSWERS` with `step_index` |
| Invalid | Outdated | 409 `REPORT_FLOW_OUTDATED`, and the client fetches the flow again and restarts the walk |
## Report flow object
### Structure
| Field | Type | Description |
| --- | --- | --- |
| target_type | string | [Report flow target type](#report-flow-target-types) |
| surface | string | [Report flow surface](#report-flow-surfaces) |
| revision_hash | string | The [revision hash](#revision-hash) of this variant (16 hexadecimal characters) |
| locale | string | The [locale](/topics/locales/) the copy was rendered in |
| start_screen_id | string | The ID of the screen a walk starts on |
| guidelines_url | ?string | The instance's community guidelines page, or null when the instance has none |
| screens | array[[report flow screen](#report-flow-screen-object) object] | Every screen of the variant |
| notices | array[[report flow notice](#report-flow-notice-object) object] | Every notice an `end` outcome lists |
### Example
```json
{
"target_type": "user",
"surface": "dsa",
"revision_hash": "9c41d2a07e5b18f3",
"locale": "en-US",
"start_screen_id": "profile_parts",
"guidelines_url": "https://example.com/guidelines",
"screens": [
{
"id": "profile_parts",
"title": "Which parts of their profile are a problem?",
"subtitle": "Pick as many as you need.",
"urgent": false,
"options": [],
"options_heading": null,
"checklist": {
"items": [
{"id": "photo", "label": "Pictures", "description": "What they use as avatar and banner"},
{"id": "name", "label": "Names", "description": "Username, display name or community nickname"}
],
"min_checked": 1,
"outcome": {"type": "screen", "screen_id": "root_user", "reason": null, "notice_id": null, "url": null}
},
"next_screen_id": null
}
],
"notices": []
}
```
## Report flow screen object
### Structure
| Field | Type | Description |
| --- | --- | --- |
| id | string | The screen ID, unique within the flow |
| title | string | The question or heading |
| subtitle | ?string | Text shown under the title |
| urgent | boolean | Whether the screen covers threats, self-harm, a risk to a minor or another serious harm, and needs an urgency notice |
| options | array[[report flow option](#report-flow-option-object) object] | The options in display order, empty on a checklist screen |
| options_heading | ?string | A heading shown above the options |
| checklist | ?[report flow checklist](#report-flow-checklist-object) object | The checklist, set only on a checklist screen |
| next_screen_id | ?string | The screen the Next button leads to, set only on an info screen |
## Report flow option object
### Structure
| Field | Type | Description |
| --- | --- | --- |
| id | string | The option ID, unique within its screen |
| label | string | The option text |
| outcome | [report flow outcome](#report-flow-outcome-object) object | What choosing the option does |
## Report flow outcome object
Every field is present, and the ones that don't apply to `type` are null.
### Structure
| Field | Type | Description |
| --- | --- | --- |
| type | string | [Report flow outcome type](#report-flow-outcome-types) |
| screen_id | ?string | The next screen when `type` is `screen` |
| reason | ?string | The [report reason](#report-reasons) when `type` is `submit` |
| notice_id | ?string | The notice to show when `type` is `end`, or null for the thank-you screen |
| url | ?string | The page to open when `type` is `link` |
## Report flow checklist object
### Structure
| Field | Type | Description |
| --- | --- | --- |
| items | array[[report flow checklist item](#report-flow-checklist-item-object) object] | The items in display order |
| min_checked | integer | The fewest items the reporter must tick |
| outcome | [report flow outcome](#report-flow-outcome-object) object | Where the screen leads, a `screen` or `submit` outcome |
## Report flow checklist item object
### Structure
| Field | Type | Description |
| --- | --- | --- |
| id | string | The item ID, unique within its checklist |
| label | string | The item text |
| description | ?string | A second line shown under the label |
## Report flow notice object
A notice says why a walk ended without a report.
### Structure
| Field | Type | Description |
| --- | --- | --- |
| id | string | The notice ID |
| title | string | The notice heading |
| body | string | The notice text |
## Report flow step object
A step is one answered screen in a submission. A choice screen's step sends `option_id`, a checklist screen's step sends `item_ids` and an info screen's step sends neither.
### Structure
| Field | Type | Description |
| --- | --- | --- |
| screen_id | string | The ID of the screen (1-48 characters) |
| option_id? | string | The ID of the chosen option (1-48 characters) |
| item_ids? | array[string] | The IDs of the ticked items (1-32 IDs of 1-48 characters) |
## Report object
### Structure
| Field | Type | Description |
| --- | --- | --- |
| report_id | snowflake | The ID of the report |
| status | string | [Report status](#report-status-values), always `pending` on a new report |
| reported_at | ISO8601 timestamp | When the report was filed |
## Success object
### Structure
| Field | Type | Description |
| --- | --- | --- |
| ok | boolean | Always true |
## Ticket object
### Structure
| Field | Type | Description |
| --- | --- | --- |
| ticket | string | The credential for [Create DSA report](#create-dsa-report), valid for one hour |
## Report status values
| Value | Description |
| --- | --- |
| pending | No moderator has resolved the report |
| resolved | A moderator closed the report |
| unknown | A status this API version doesn't know |
## Report flow target types
| Value | Description |
| --- | --- |
| message | A message |
| user | A user profile |
| guild | A guild |
## Report flow surfaces
| Value | Description |
| --- | --- |
| in_app | The flow a signed-in client shows (the default) |
| dsa | The flow the public Digital Services Act form shows |
## Report flow outcome types
| Value | Description |
| --- | --- |
| screen | Go to the screen in `screen_id` |
| submit | Show a summary, then file a report under `reason` |
| end | Finish without a report and show the notice in `notice_id`, or a thank-you screen |
| link | Open `url` and stay on the current screen |
## Report reasons
A report filed through a flow stores one of these reasons. Each reason maps to a [category](#report-categories) for each target type, and [List report reasons](/admin-api/reports/#list-report-reasons) returns that mapping. Handle a reason value you don't know, because new reasons can appear.
| Value | Description |
| --- | --- |
| spam | Spam |
| fake_account | Fake or deceptive account |
| platform_abuse | Scraping, automation or other platform abuse |
| account_trading | Buying or selling accounts, logins or card details |
| metric_manipulation | Faked member or reaction counts |
| harassment | Harassment or bullying |
| unwanted_contact | Stalking or unwanted contact |
| raid | Raid or coordinated attack |
| false_claims_about_person | False claims used to target a person |
| hate_slurs | Slurs, hateful symbols or stereotypes |
| hate_dehumanizing | Dehumanizing a group |
| hate_incitement | Calls for violence or exclusion against a group |
| atrocity_denial | Genocide or atrocity denial or celebration |
| lgbtq_targeting | Misgendering, deadnaming, outing or identity denial |
| conversion_therapy | Promoting conversion therapy |
| hate_other | Other attacks on people for who they are |
| violent_threat | Threat of violence |
| violence_incitement | Encouraging violence or instructions to harm |
| violence_glorification | Glorifying real-world violence |
| graphic_violence | Real violence shown to shock |
| terrorism_extremism | Terrorism or violent extremism |
| harmful_false_claims | False claims likely to cause serious harm |
| deceptive_synthetic_media | Fake or AI media presented as real |
| sexual_unwanted | Sexual images or messages nobody asked for |
| adult_content_unmarked | Adult content outside an 18+ space |
| intimate_image_abuse | Intimate images shared without consent |
| sexual_exploitation | Sexual exploitation, coercion or trafficking |
| minor_fictional_sexualization | Sexualized fictional child |
| minor_sexualization | Sexual comments about minors |
| minor_sexual_contact | Flirting with or sexually messaging a minor |
| minor_sexual_content | A minor sharing sexual content themselves |
| csam | Child sexual abuse material |
| minor_grooming | Grooming a minor |
| minor_contact | Predatory contact with a minor |
| minor_in_adult_space | A minor in an 18+ space |
| minor_dating_community | Community for dating between minors |
| doxxing | Private information shared without consent |
| underage | Under the minimum age |
| wellbeing_concern | Worried about someone's safety |
| self_harm_promotion | Encouraging self-harm or sharing methods |
| suicide_promotion | Encouraging suicide |
| eating_disorder_promotion | Encouraging disordered eating |
| self_harm_graphic | Graphic self-harm images |
| self_harm_pressure | Pressuring someone to harm themselves |
| impersonation_staff | Pretending to be staff or support |
| impersonation_person | Impersonating a person |
| impersonation_public_figure | Impersonating a well-known person |
| impersonation_organization | Impersonating a company, brand or group |
| fraud | Conning people out of money or accounts |
| illegal_goods | Drug, weapon or other illegal sales |
| illegal_activity | Other illegal activity |
| malware_phishing | Phishing, malware or hacking attempts |
| ban_evasion | Getting around a ban |
| permits_violations | Community allows serious rule-breaking |
| copyright | Copyright or trademark complaint |
| rude_language | Swearing or rude remarks |
| other | Something not listed |
## Report categories
Every report stores one of these categories.
| Value | Description |
| --- | --- |
| harassment | Harassment, bullying or intimidation |
| hate_speech | Hatred against protected groups |
| violent_content | Content showing or promoting violence |
| extremist_community | A guild promoting extremist or terrorist ideologies |
| raid_coordination | A guild coordinating attacks on other communities |
| spam | Unsolicited bulk messages or promotional content |
| spam_account | An account used for spamming |
| nsfw_violation | Adult content outside age-restricted channels |
| inappropriate_profile | Inappropriate or offensive profile content |
| illegal_activity | Content promoting or facilitating illegal activities |
| doxxing | Content revealing private personal information |
| self_harm | Content promoting self-harm or suicide |
| child_safety | Content that endangers minors or shows child abuse |
| underage_user | Someone who appears to be under the minimum age |
| malicious_links | Links to malware, phishing or other malicious sites |
| malware_distribution | Distribution of malware |
| impersonation | Falsely claiming to be another person or entity |
| other | Anything the other categories don't cover |
## EU country codes
| Value | Description |
| --- | --- |
| AT | Austria |
| BE | Belgium |
| BG | Bulgaria |
| HR | Croatia |
| CY | Cyprus |
| CZ | Czechia |
| DK | Denmark |
| EE | Estonia |
| FI | Finland |
| FR | France |
| DE | Germany |
| GR | Greece |
| HU | Hungary |
| IE | Ireland |
| IT | Italy |
| LV | Latvia |
| LT | Lithuania |
| LU | Luxembourg |
| MT | Malta |
| NL | Netherlands |
| PL | Poland |
| PT | Portugal |
| RO | Romania |
| SK | Slovakia |
| SI | Slovenia |
| ES | Spain |
| SE | Sweden |
## Get report flow
<RouteHeader method="GET" path="/v1/reports/flows/{target_type}" unauthenticated />
Returns the [report flow object](#report-flow-object) for one [target type](#report-flow-target-types) and surface, translated into one locale.
### Query parameters
| Field | Type | Description |
| --- | --- | --- |
| surface? | string | [Report flow surface](#report-flow-surfaces) (default `in_app`) |
| locale? | string | The language tag to translate into (1-35 characters), defaulting to the [request locale](/topics/locales/#negotiation) |
### Response
| Status | Body | Condition |
| --- | --- | --- |
| 200 | [report flow](#report-flow-object) object | The flow was returned |
| 400 | [error response](/http-api/#error-response) | `INVALID_FORM_BODY` for an unknown target type or surface |
The rate limit is 40 requests per 10 seconds, on the `report:list` bucket.
## Submit message report flow
<RouteHeader method="POST" path="/v1/reports/flows/message/submissions" />
Files a report about a message from the reporter's answers to the `in_app` message flow and returns a [report object](#report-object). It needs a user session token, and the reporter must be able to read the message.
### JSON body
| Field | Type | Description |
| --- | --- | --- |
| channel_id | snowflake | The ID of the channel the message is in |
| message_id | snowflake | The ID of the reported message |
| revision_hash | string | The [revision hash](#revision-hash) of the flow the reporter answered (1-64 characters) |
| steps | array[[report flow step](#report-flow-step-object) object] | The answered screens in walk order (1-16 steps) |
| locale? | string | The language tag the reporter saw the flow in (1-35 characters) |
### Response
| Status | Body | Condition |
| --- | --- | --- |
| 200 | [report](#report-object) object | The report was filed |
| 400 | [error response](/http-api/#error-response) | `INVALID_REPORT_FLOW_ANSWERS` when the answers don't fit the current flow |
| 400 | [error response](/http-api/#error-response) | `UNCLAIMED_ACCOUNT_CANNOT_SUBMIT_REPORTS` for an unclaimed account while `interaction_tier` is `legacy` |
| 400 | [error response](/http-api/#error-response) | `CANNOT_REPORT_OWN_MESSAGE` when the reporter wrote the message |
| 403 | [error response](/http-api/#error-response) | `REPORT_EMAIL_VERIFICATION_REQUIRED` for an unverified email while `interaction_tier` is `legacy` |
| 403 | [error response](/http-api/#error-response) | `REPORT_BANNED` when the account is banned from reporting |
| 403 | [error response](/http-api/#error-response) | `MISSING_PERMISSIONS` when the reporter can't view the channel |
| 404 | [error response](/http-api/#error-response) | `UNKNOWN_CHANNEL` or `UNKNOWN_MESSAGE` when the reporter can't see the channel or message |
| 404 | [error response](/http-api/#error-response) | `UNKNOWN_USER` when the author's account no longer exists |
| 409 | [error response](/http-api/#error-response) | `REPORT_FLOW_OUTDATED` when the answers came from an outdated flow |
| 409 | [error response](/http-api/#error-response) | `CONFLICT` when the reporter reported this message in the last 365 days |
The rate limit is 10 requests per hour, on the `report:create` bucket. One reporter can file at most 5 reports an hour across the report routes, and [Rate limits](/topics/rate-limits/#limits-that-return-429) lists the lower limits for one channel, guild or message. A report whose reason is one of the highest-priority reasons doesn't count toward the reporter's hourly, channel or guild limits. When [`interaction_tier`](/http-api/users/#account-tiers) is `enforced`, an account that isn't verified can still report, up to 5 reports a day for the account and 10 a day from one IP address. On any instance, an account that isn't verified can still file a report whose reason is one of the highest-priority reasons, such as child safety, threats, intimate image abuse or self-harm, within the same daily limits.
## Submit user report flow
<RouteHeader method="POST" path="/v1/reports/flows/user/submissions" />
Files a report about a user's profile from the reporter's answers to the `in_app` user flow and returns a [report object](#report-object). It needs a user session token.
### JSON body
| Field | Type | Description |
| --- | --- | --- |
| user_id | snowflake | The ID of the reported user |
| guild_id? | snowflake | The ID of the guild the reporter saw the profile in |
| revision_hash | string | The [revision hash](#revision-hash) of the flow the reporter answered (1-64 characters) |
| steps | array[[report flow step](#report-flow-step-object) object] | The answered screens in walk order (1-16 steps) |
| locale? | string | The language tag the reporter saw the flow in (1-35 characters) |
### Response
| Status | Body | Condition |
| --- | --- | --- |
| 200 | [report](#report-object) object | The report was filed |
| 400 | [error response](/http-api/#error-response) | `INVALID_REPORT_FLOW_ANSWERS` when the answers don't fit the current flow |
| 400 | [error response](/http-api/#error-response) | `UNCLAIMED_ACCOUNT_CANNOT_SUBMIT_REPORTS` for an unclaimed account while `interaction_tier` is `legacy` |
| 400 | [error response](/http-api/#error-response) | `CANNOT_REPORT_YOURSELF` when the report is about the reporter's own account |
| 403 | [error response](/http-api/#error-response) | `REPORT_EMAIL_VERIFICATION_REQUIRED` for an unverified email while `interaction_tier` is `legacy` |
| 403 | [error response](/http-api/#error-response) | `REPORT_BANNED` when the account is banned from reporting |
| 404 | [error response](/http-api/#error-response) | `UNKNOWN_USER` when `user_id` isn't an account, or is the system account |
| 404 | [error response](/http-api/#error-response) | `UNKNOWN_GUILD` when `guild_id` isn't a guild the reporter is in |
| 409 | [error response](/http-api/#error-response) | `REPORT_FLOW_OUTDATED` when the answers came from an outdated flow |
| 409 | [error response](/http-api/#error-response) | `CONFLICT` when the reporter reported this user in the last 24 hours |
The rate limit is 10 requests per hour, on the `report:create` bucket. One reporter can file at most 5 reports an hour across the report routes, and a report whose reason is one of the highest-priority reasons doesn't count toward that limit. When [`interaction_tier`](/http-api/users/#account-tiers) is `enforced`, an account that isn't verified can still report, up to 5 reports a day for the account and 10 a day from one IP address. On any instance, an account that isn't verified can still file a report whose reason is one of the highest-priority reasons, such as child safety, threats, intimate image abuse or self-harm, within the same daily limits.
## Submit community report flow
<RouteHeader method="POST" path="/v1/reports/flows/guild/submissions" />
Files a report about a guild from the reporter's answers to the `in_app` guild flow and returns a [report object](#report-object). It needs a user session token, and the reporter must be a member of the guild, the guild must be discoverable, or the request must include an invite code for the guild.
### JSON body
| Field | Type | Description |
| --- | --- | --- |
| guild_id | snowflake | The ID of the reported guild |
| invite_code? | string | An invite code for the guild that the reporter used to see it (1-64 characters) |
| revision_hash | string | The [revision hash](#revision-hash) of the flow the reporter answered (1-64 characters) |
| steps | array[[report flow step](#report-flow-step-object) object] | The answered screens in walk order (1-16 steps) |
| locale? | string | The language tag the reporter saw the flow in (1-35 characters) |
### Response
| Status | Body | Condition |
| --- | --- | --- |
| 200 | [report](#report-object) object | The report was filed |
| 400 | [error response](/http-api/#error-response) | `INVALID_REPORT_FLOW_ANSWERS` when the answers don't fit the current flow |
| 400 | [error response](/http-api/#error-response) | `UNCLAIMED_ACCOUNT_CANNOT_SUBMIT_REPORTS` for an unclaimed account while `interaction_tier` is `legacy` |
| 400 | [error response](/http-api/#error-response) | `CANNOT_REPORT_OWN_GUILD` when the reporter owns the guild |
| 403 | [error response](/http-api/#error-response) | `REPORT_EMAIL_VERIFICATION_REQUIRED` for an unverified email while `interaction_tier` is `legacy` |
| 403 | [error response](/http-api/#error-response) | `REPORT_BANNED` when the account is banned from reporting |
| 403 | [error response](/http-api/#error-response) | `CANNOT_REPORT_GUILD` when the reporter isn't a member, the guild isn't discoverable and no invite code for it was sent |
| 404 | [error response](/http-api/#error-response) | `UNKNOWN_GUILD` when `guild_id` isn't a guild |
| 409 | [error response](/http-api/#error-response) | `REPORT_FLOW_OUTDATED` when the answers came from an outdated flow |
| 409 | [error response](/http-api/#error-response) | `CONFLICT` when the reporter reported this guild in the last 24 hours |
The rate limit is 10 requests per hour, on the `report:create` bucket. One reporter can file at most 5 reports an hour across the report routes, and a report whose reason is one of the highest-priority reasons doesn't count toward that limit. When [`interaction_tier`](/http-api/users/#account-tiers) is `enforced`, an account that isn't verified can still report, up to 5 reports a day for the account and 10 a day from one IP address. On any instance, an account that isn't verified can still file a report whose reason is one of the highest-priority reasons, such as child safety, threats, intimate image abuse or self-harm, within the same daily limits.
## Send DSA report email
<RouteHeader method="POST" path="/v1/reports/dsa/email/send" unauthenticated />
Sends a Digital Services Act verification code to an email address and returns a [success object](#success-object). The code expires after 10 minutes, and one address can get one code per minute and 3 per hour.
### JSON body
| Field | Type | Description |
| --- | --- | --- |
| email | string | The address that gets the code (1-254 characters) |
### Response
| Status | Body | Condition |
| --- | --- | --- |
| 200 | [success](#success-object) object | The code was sent |
| 400 | [error response](/http-api/#error-response) | `EMAIL_UNAVAILABLE_ON_INSTANCE` when the instance uses username sign-in |
| 400 | [error response](/http-api/#error-response) | `INVALID_FORM_BODY` when the address is invalid or its domain can't receive mail |
| 503 | [error response](/http-api/#error-response) | `SERVICE_UNAVAILABLE` when the email couldn't be sent |
The rate limit is 5 requests per hour, on the `dsa:report:email:send` bucket.
## Verify DSA report email
<RouteHeader method="POST" path="/v1/reports/dsa/email/verify" unauthenticated />
Exchanges a verification code for a [ticket object](#ticket-object). Each address gets 5 attempts in 10 minutes, and a sixth attempt deletes the code until you send a new one.
### JSON body
| Field | Type | Description |
| --- | --- | --- |
| email | string | The address that got the code (1-254 characters) |
| code | string | The code in `XXXX-XXXX` form |
### Response
| Status | Body | Condition |
| --- | --- | --- |
| 200 | [ticket](#ticket-object) object | The code matched |
| 400 | [error response](/http-api/#error-response) | `INVALID_DSA_VERIFICATION_CODE` when the code is wrong or expired, or attempts ran out |
| 400 | [error response](/http-api/#error-response) | `EMAIL_UNAVAILABLE_ON_INSTANCE` when the instance uses username sign-in |
The rate limit is 10 requests per hour, on the `dsa:report:email:verify` bucket.
## Create DSA report
<RouteHeader method="POST" path="/v1/reports/dsa" unauthenticated />
Files a Digital Services Act notice about a message, user or guild and returns a [report object](#report-object). Walk the flow with `surface=dsa` and send the fields for your `report_type`. The ticket is used up only when the notice is filed.
### JSON body
#### Common fields
| Field | Type | Description |
| --- | --- | --- |
| ticket | string | The ticket from [Verify DSA report email](#verify-dsa-report-email) (1-128 characters) |
| report_type | string | The [target type](#report-flow-target-types) of the notice |
| revision_hash | string | The [revision hash](#revision-hash) of the `dsa` flow the reporter answered (1-64 characters) |
| steps | array[[report flow step](#report-flow-step-object) object] | The answered screens in walk order (1-16 steps) |
| additional_info | string | The reporter's explanation of the problem (1-1000 characters) |
| good_faith_confirmed | boolean | Must be `true`, confirming the notice is accurate and complete |
| reporter_full_legal_name?<sup>1</sup> | string | The reporter's full legal name (1-160 characters) |
| reporter_country_of_residence | string | The reporter's [EU country code](#eu-country-codes) |
| locale? | string | The language tag the reporter saw the flow in (1-35 characters) |
<sup>1</sup> Required unless the walk ends in the `child_safety` category
#### Message fields
| Field | Type | Description |
| --- | --- | --- |
| message_link<sup>1</sup> | string | The link to the reported message (1-2048 characters) |
| reported_user_tag? | string | The author's tag in `username#1234` form, or the username (1-37 characters) |
<sup>1</sup> An absolute URL with the path `/channels/{guild_id}/{channel_id}/{message_id}`, with `@me` in place of the guild ID for a direct message
#### User fields
| Field | Type | Description |
| --- | --- | --- |
| user_id?<sup>1</sup> | snowflake | The ID of the reported user |
| user_tag?<sup>1</sup> | string | The user's tag in `username#1234` form, or the username (1-37 characters) |
<sup>1</sup> Send at least one, and when you send both they must be the same account
#### Guild fields
| Field | Type | Description |
| --- | --- | --- |
| guild_id | snowflake | The ID of the reported guild |
| invite_code? | string | An [invite](/http-api/invites/) code or URL for the guild (1-64 characters) |
### Response
| Status | Body | Condition |
| --- | --- | --- |
| 200 | [report](#report-object) object | The notice was filed |
| 400 | [error response](/http-api/#error-response) | `INVALID_DSA_TICKET` when the ticket is unknown or expired |
| 400 | [error response](/http-api/#error-response) | `INVALID_DSA_REPORT_TARGET` when the user ID and tag point to different accounts, or the invite isn't for `guild_id` |
| 400 | [error response](/http-api/#error-response) | `INVALID_REPORT_FLOW_ANSWERS` when the answers don't fit the current `dsa` flow |
| 404 | [error response](/http-api/#error-response) | `UNKNOWN_MESSAGE` when the message link or author tag doesn't match a message |
| 404 | [error response](/http-api/#error-response) | `UNKNOWN_USER`, `UNKNOWN_GUILD` or `UNKNOWN_INVITE` when the reported user, guild or invite doesn't exist |
| 409 | [error response](/http-api/#error-response) | `REPORT_FLOW_OUTDATED` when the answers came from an outdated flow |
The rate limit is 5 requests per hour, on the `dsa:report:create` bucket.