Video moderation

Input

Submit a multipart/form-data request with:

Field	Type	Required	Description
`video`	string	Yes	Publicly reachable HTTP or HTTPS URL of the video to scan, up to 100 MB. The API fetches it.
`webhook_url`	string	No	URL to receive the result on completion.

curl -X POST https://api.omnifence.ai/api/v1/moderate/video \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "video=https://storage.example.com/generated/output.mp4"

The video field must be a public HTTP or HTTPS URL. URLs using another scheme, or resolving to a private or internal network address, are rejected with 400 INVALID_REQUEST. The linked video must be no larger than 100 MB.

Checks

AI Adult General

The clip is analysed for the always-on AI Adult General policy, which covers prohibited adult content and content that depicts, or appears to depict, a minor in a sexual or exploitative context. It also folds in any enabled custom categories. This check cannot be disabled.

NSFW label

When the NSFW check is enabled, the informational nsfw boolean is returned alongside the decision. It never causes a rejection on its own.

Output

{
  "is_prohibited": false,
  "nsfw": false,
  "job_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
  "type": "video",
  "status": "completed",
  "created_at": "2026-05-19T12:00:00.000Z",
  "completed_at": "2026-05-19T12:00:08.000Z"
}

On a rejection, a reason field explains what tripped. The nsfw field is only present when the NSFW check is enabled. See decision logic for how the prohibition decision is determined.

Getting started

Platform

Moderation

Input

Checks

AI Adult General

NSFW label

Output

Latency

​Input

​Checks

​AI Adult General

​NSFW label

​Output

​Latency

Input

Checks

AI Adult General

NSFW label

Output

Latency