Reports v2: Sample Use Cases and Flows

This article shares some possible use cases of the API. You are not limited to these use cases, but they can be a helpful jumping off point as you plan on how to use this API.

Track reasons for content reports

You can analyze user-reported issues and identify recurring problems in the site's content. This helps site owners make informed decisions about updating community guidelines and implementing stricter content rules. For example, if the analysis reveals that a majority of reports cite "spam" as the issue, the site owner can implement automated spam detection tools and update community guidelines to address the problem proactively.

To track reasons for content reports:

1. Call Count Reports by Reason Types to retrieve the reasonTypeCount array, and pass it to your data analysis tool for processing.
2. On an ongoing basis, listen for the Report Created and Report Updated webhooks. Extract the reason field from these events and send it to your data analysis tool to update your calculations in real time.