Video
4 min
nima allows you to automatically detect harmful videos using powerful ai detection providers example payload { "priority" "severe", "channel" "automated detection", "reason for request" "lorem abuse reason for request", "customerspecific" { }, "content" { "content id" "098765434567", "title" "sniper video", "body" "forest walk holding weapon", "url" "https //videos pexels com/video files/6201055/6201055 uhd 3840 2160 25fps mp4", "token" "", "type" { "id" "video static" }, "status" "published", "customerspecific" {} }, "reportee" { "id" "123", "name" "reportee john", "lang" "en", "phonenumber" "070 564123", "emailaddress" "reportee\@tremau net", "customerspecific" {} }, "label" \[ "weapon" ] } request payload requirements for video moderation, ensure your request payload includes the following content type specific requirements attribute required description content url yes for video based moderation, the url should point to the video if the url provided is intended to display an entire page, please see "detecting harmful pages" content type id yes must be set to "video static" configuring detection rules to create a rule for automated video detection, navigate to admin settings > workflow configuration and define the following conditions required conditions channel must be set to "proactive detection" content type must be set to "video static" once these conditions are set, the list of available ai detection providers will be accessible via the choose provider button audio profanity detection for video sightengine supports audio profanity detection for video content (video static type) this allows you to moderate both the visual and audio components of videos in a single request when configuring a rule for video content with audio profanity detection set the content type to video static select sightengine as the provider choose the audio profanity class the detection processes synchronously and returns profanity matches found in the video's soundtrack along with a transcription videos without sound are handled gracefully—the system processes the content normally without the audio profanity component