API Documentation
Illegal Content Report Form
5 min
this page provides technical implementation details for integrating nima's docid\ ivu2yjpwt2iqfgipinqtm illegal content report form into your platform this form enables your users to submit compliant reports for illegal content across multiple jurisdictions for regulatory context and compliance features , see in the compliance section this form is different from your form and is specifically designed to comply with illegal content reporting obligations such as those under the eu digital services act, uk online safety act, and other regulatory frameworks when you link this form to your platform, it will appear white labeled and be available to your users to submit reports directly the sequence diagram below describes the flow of interaction between your platform and nima server to serve the form to your users form display and submission to integrate the illegal content reporting form into your platform link the form connect your report call to action button to the nima form url provided during your onboarding phase pass parameters include the required parameters in the form url query string as url encoded values required parameters true 337,337 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type optional parameters you can pass additional custom fields via the following attributes content customerspecific location customerspecific reporter customerspecific reportee customerspecific customerspecific (global attributes) example if you want to pass a parameter specifying the type of image reported ("galleryitem", "profile", "shoplisting", etc ), you can store the value in content customerspecific imagetype because it is a property related to the content true 224,224,226 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type what happens next when a user clicks your report cta, they are redirected to the white labeled form hosted by nima the user fills out the form with the necessary information and submits their report upon submission, nima creates a report with the parameters you configured in step 2, and automatically sends a confirmation notification to the reporter acknowledging receipt of their report, if set up in configure an endpoint in nima to pull complementary information to enrich reports with additional data from your platform in nima, navigate to admin settings > client configuration specify an endpoint that nima can call to retrieve complementary information about the reportee this endpoint receives one parameter the content id of the content being reported map your endpoint's response fields to the nima schema using the mapping ui tool in the client configuration screen click save configuration to apply your changes configure rule routing to ensure reports from the illegal content form are properly routed to your moderation queues navigate to admin settings > or in nima create or edit routing rules and set the source field to "illegal content report form" define the queue routing logic based on your moderation workflow this configuration ensures that reports submitted through the form are correctly identified and directed to the appropriate moderation queues for review report display to content moderators once a report is submitted before the report is displayed in the nima moderation console, nima will call your configured api endpoint to fetch complementary information (if configured) the content moderator reviews the report and takes a moderation decision