Client URL configuration and content history

the client url configuration enables nima to maintain secure, real time communication with your servers after a report has been submitted this capability is essential for both enriching the report data and ensuring that moderators are always reviewing the most current version of the content the role of the client url the configured url is used by nima's moderation platform to query your servers for supplementary information or updated content details, providing a seamless data flow between your platform and nima key use cases data enrichment when a report is submitted via nima’s self hosted forms, the configured url is used to pull complementary information from your servers, providing the moderator with a complete context for the case content recency and history just before a moderator begins reviewing a case, the configured url is used to pull the latest version of the content this ensures the moderator acts on the content as it currently exists on your platform any changes introduced by the content uploader since the original report was filed are logged and displayed to the moderator upon request configuring the client url configure it in configure > api & integration > data fetch enable the integration refresh content — turn this on to allow nima to call your platform for the latest version of the content with it off, moderators review the content exactly as it was captured when the report was filed endpoint — the url on your platform that nima calls to retrieve content authenticating the call most platforms protect this endpoint nima supports two approaches, and you can use either or both header authentication — set a header key and header value , sent with every request this suits a static api key or shared secret oauth — switch on enable oauth and provide endpoint — your oauth token endpoint (this is separate from the content endpoint above) grant type — client credentials or password select none to disable oauth while keeping the configuration client id and client secret — your oauth application credentials username and password — required only for the password grant type; these fields are hidden for client credentials scope — the scope requested with the token, if your authorisation server expects one nima requests a token before calling your endpoint and refreshes it as needed mapping the response your endpoint's response is unlikely to match nima's field names exactly, so the configuration includes a mapping that tells nima where to find each value in the json you return — for example, which path holds the content title set one entry per field you want nima to read this endpoint is called just before a moderator opens a case if it is slow or unavailable, moderators wait — so treat its latency and uptime as part of your moderation tooling rather than as a background integration