Livestream

nima allows you to automatically detect harmful content in livestreams using powerful ai detection providers example payload { "priority" "high", "channel" "user report", "reason for request" "this video is a live stream", "note" "this video is a live stream", "customerspecific" {}, "content" { "content id" "some content id xxx", "title" "title for live stream", "body" "body for live stream", "url" "https //zssd kijami hls camzonecdn com/camzonestreams/zssd kijami/playlist m3u8", "language" "en", "token" "", "type" { "id" "video stream", "name" "video stream" }, "status" "published", "customerspecific" { } }, "reporter" { "id" "reporter id xxx", "name" "reporter id name", "phonenumber" "reporter phone number", "emailaddress" "reporter email address", "customerspecific" {} }, "reportee" { "id" "reportee id", "name" "reportee name", "phonenumber" "reportee phone numner", "emailaddress" "reportee email address", "customerspecific" {} }, "location" { "city" "location city", "postalcode" "location postal code", "region" "location region", "countrycode" "location country code", "ipaddress" "location id address", "customerspecific" {} }, "label" \[ "stream" ] } request payload requirements for livestream moderation, ensure your request payload includes the following content type specific requirements true 314,314,315 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 for all other payload parameters, please refer to the docid\ fhlq7h pq8ibh7ocl2dza documentation configuring detection rules to create a rule for automated livestream 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 stream" once these conditions are set, the list of available ai detection providers will be accessible via the choose provider button livestream specific features how it works your backend submits a livestream to nima api the livestream analyzer monitors the stream in real time and creates alerts each time unwanted content is detected moderation results are sent to nima as they occur available detection models the following detection models are commonly used for livestream moderation (for a full list, please contact support) true 471,472 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 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 left unhandled content type left unhandled content type supported protocols the livestream api supports the following protocols for live video ingestion hls (http live streaming) over https or http rtmp and rtmps (real time messaging protocol) rtsp and rtp (real time streaming protocol) mpeg dash (mpeg dynamic adaptive streaming over http)