Intro to our Technical Documentation

what does it mean to integrate nima? integrating with nima means connecting your platform so that any content or account whether reported by users, any ai detection provider, or regulators is ingested into nima for review and enforcement once a case is in nima, your automated rules, ai agents or your trust & safety team can review it, apply policies, and trigger enforcement actions back on your platform via fully customisable webhooks the integration is lightweight there is a single endpoint, and the same payload structure covers every ingestion source, with only the channel and content type fields changing thus, you do not need separate integrations for different content types or reporting sources the single endpoint all content submissions are sent to one endpoint post https //api {your tenant id} com/endpoint moderation note your exact base url and endpoint is provided by tremau during onboarding the two fields that change the payload structure is identical across all use cases only two fields vary between submissions channel and content type channel tells nima which ingestion source the report is coming from this determines how the case is routed through the rule engine and which moderation queues it lands in channel value use case proactive detection content submitted for proactive ai based scanning user report illegal content illegal content report submitted via the nima hosted compliance form — no api integration required, the form is already wired to nima user report a user on your platform has reported content for review through your own forms trusted flagger report submitted by a designated trusted flagger lea request received from a law enforcement agency content type tells nima what kind of content is being submitted the same endpoint accepts all supported content types — you set this per submission so nima routes it to the correct ai detection provider and displays it correctly in the moderation console content type value content txt text img image video static pre recorded video video stream livestream audio audio iframe iframe file file how a case moves through nima your platform sends a post request to the single endpoint nima's rule engine evaluates the case against your configured policies and thresholds the case is routed either to a moderation queue for human review or is automatically actioned if an ai detection provider rule fires an automated enforcement when an enforcement action is applied, nima fires a webhook back to your configured endpoint with the outcome and case data that you can fully customise keeping content fresh with client url configuration nima can call back to your servers either when a report is submitted to nima or just before a moderator opens a case to fetch the latest version of the content and to pull complementary data from your platform and enrich the information this ensures your ai agents or moderators always act on current content, not a snapshot from the time of the original report configuring a client url is optional but strongly recommended for platforms where content can be edited or removed after it has been reported see client url configuration and content history docid\ sqpuak32eagwqpx xg1qr for setup details before you begin make sure the following are in place before sending your first request your tenant api base url (provided by tremau during onboarding) at least one moderation queue configured in nima rules configured under settings > trust & safety > rules to route incoming cases for proactive detection ai provider credentials configured in the ai marketplace — ask the tremau support team