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, 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.
A report flow is the set of screens a reporter answers before a report is filed. 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 until one has the type submit, and this path is the walk. Each screen on the walk adds one step 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 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
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.
A report filed through a flow stores one of these reasons. Each reason maps to a category for each target type, and 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
Files a report about a message from the reporter's answers to the in_app message flow and returns a report object. It needs a user session token, and the reporter must be able to read the message.
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 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 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.
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 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.
Files a report about a guild from the reporter's answers to the in_app guild flow and returns a 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.
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 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.
Sends a Digital Services Act verification code to an email address and returns a success object. The code expires after 10 minutes, and one address can get one code per minute and 3 per hour.
Exchanges a verification code for a ticket object. Each address gets 5 attempts in 10 minutes, and a sixth attempt deletes the code until you send a new one.
Files a Digital Services Act notice about a message, user or guild and returns a 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.