is_prohibited decision on those jobs, so
disabling either optional check still leaves them fully covered. See
moderation categories.
Text jobs work differently: they have no image or video to evaluate, so their is_prohibited
decision comes from the text check alone. Disabling the text toggle therefore removes the only
check those jobs have, and every text job passes. Audio jobs are checked on their transcript by
the same text check, but that check is not covered by the text toggle and always runs.
By default, both optional checks are enabled.
Where to configure
Open the Moderation page in the customer dashboard. Each check appears as a tile with a toggle. Changes are saved immediately and apply to all subsequent jobs.Available toggles
How disabled checks behave
nsfwdisabled: the NSFW check is skipped and thensfwfield is omitted from the job result and the webhook payload. The prohibited decision is unaffected.textdisabled: the text check is skipped for text jobs, and with it every custom category. Those jobs have no other check, so every one of them passes. Image, video, and audio jobs are unaffected. Audio still runs the same check on its transcript, custom categories included.
Custom categories
Custom categories have their own enable/disable flag, set per category rather than through this endpoint. An enabled category runs on image, video, text and audio, but thetext toggle still
wins over it. With text disabled, text jobs run no check at all, so the API evaluates none of your
custom categories on them. See custom categories.
API access
You can also read and update your toggles from the API.Read current settings
enabled_categories object contains only the checks you have explicitly disabled. Anything
missing is enabled. The catalogue provides human-readable labels and descriptions for each toggle.
Update settings
nsfw and
text; values must be booleans. Any other key returns 400 INVALID_REQUEST. Sending an empty object
{} resets both checks back to their default (enabled).