Prerequisites
- A Omnifence account. Sign up at the dashboard. Your organization is provisioned automatically on first signup.
- An API key. Create one from the API Keys page in the dashboard. The raw value is shown once at creation, so copy it immediately.
- cURL or any HTTP client.
Steps
1
Authenticate
Include your API key as a Bearer token in the
Authorization header with every request.2
Submit an image moderation request
Send an image URL for moderation. The API returns a job ID immediately. Use
POST /api/v1/moderate/text to moderate text instead, or
POST /api/v1/moderate/video for a video URL, or POST /api/v1/moderate/audio for an audio clip.Response
3
Check job status
Poll the job endpoint with the returned A rejected job adds a
job_id.Response
reason that names the policy or custom category that tripped.Rejected
4
Set up a webhook (optional)
Instead of polling, register a webhook to receive results automatically.When the job completes, the API POSTs the result to your URL. The payload carries the same
decision fields as the job endpoint, plus a Every callback is signed with your account’s signing secret, following the
Standard Webhooks specification.
Verify the signature before you act on a payload — find your secret in the dashboard under
Account → Webhooks.See webhooks for verification, the full field list and the retry
behaviour.
Response
delivery_id for deduplication. It carries no type
and no created_at.Delivered payload
Next steps
Authentication
Learn how API keys work and how to manage them.
Content moderation
Understand how moderation works across each content type.
Error recovery
Recover in-flight jobs after a restart or a missed webhook.
Handle a rejection
Understand decision logic and what to do when a job is rejected.
Webhook reliability
Build reliable webhook handling with fallback polling.
API reference
Full endpoint reference with request and response schemas.