API Documentation
EU Transparency Database Integration
10 min
this guide walks you through setting up automated statement of reasons (sor) submissions to the eu transparency database to ensure compliance with the digital services act prerequisites before configuring sor submissions in nima, you'll need to complete the initial setup with the eu portal more information available https //transparency dsa ec europa eu/page/onboarding documentation 1\ create eu portal accounts you must create two separate accounts on the eu transparency database portal sandbox account for testing sor submissions production account for live sor submissions ⚠️ important the eu requires that you successfully send test sors to the sandbox environment before you can submit to production 2\ api token configuration after creating your portal accounts, you'll receive api tokens for both environments sandbox api token share this with your nima support team for initial testing and sor validation production api token this will be configured in your nima instance once sandbox testing is complete and validated process provide your sandbox api token to nima support for testing we'll validate your sor submissions in the sandbox environment once validated, tremau will configure your production instance with your production api token nima configuration requirements for nima to automatically generate and submit statement of reasons, your configuration must meet the following requirements country code configuration ensure that incoming flags contain a countrycode in the location attribute of the request payload with an eu country code why this matters nima only sends statement of reasons to the eu for content flagged within eu member countries { "location" { "countrycode" "de" // must be an eu country code } } dsa infringement categories mapping all policy configurations must have statement categories assigned navigate to settings → policy configuration for each policy configuration, ensure a dsa infringement category is assigned more details in docid\ ncsbihsujuk1eaeey bh2 save your changes why this matters statement categories are required by the eu to categorize the type of content violation action dsa decision type mapping all moderation actions must be assigned to a decision type as detailed in docid\ ncsbihsujuk1eaeey bh2 why this matters the eu requires clear decision types to understand what action was taken on flagged content how it works once all requirements are satisfied automated processing a cron job runs nightly sor generation valid statement of reasons are automatically generated for qualifying flags eu submission sors are sent to the eu transparency api puid assignment upon successful submission, a puid (platform unique identifier) is set on the flag for tracking validation checklist before going live, verify that sandbox and production accounts are created on the eu portal test sors have been successfully submitted to sandbox country codes are properly configured in request payloads all policy configurations have statement categories assigned all moderation actions have decision types mapped cron job is scheduled and running monitoring and verification portal submission tracking the eu transparency database portal provides visibility into your sor submissions sandbox portal monitoring log into your sandbox account to review test submissions verify that sors appear with correct formatting and required fields use this environment to validate your integration before production production portal monitoring access your production account to monitor live sor submissions review submission history and status for each sor track successful submissions and identify any rejected entries monitor compliance metrics and submission volumes what to monitor when checking the portal, pay attention to submission status confirm sors are being accepted (not rejected) required fields ensure all mandatory eu fields are populated correctly timing verify submissions align with your nightly cron job schedule volume check that submission counts match your expected flag volumes for eu countries next steps once your configuration is complete and validated monitor portal submissions regularly check both sandbox and production portals for successful sor submissions verify system operation confirm that the nightly cron job is running successfully and puids are being assigned to qualifying flags track compliance use the eu portal to monitor overall submission volumes and ensure regulatory compliance support if you encounter issues during setup or need assistance with eu compliance requirements, please contact our support team useful links https //transparency dsa ec europa eu/?lang=en