What does content_moderation_rejected mean on a FiveAPI video task?

Short answer: content_moderation_rejected means the video request was refused by FiveAPI's content policy. The task fails, the credit hold is released, and you should not resubmit the same input expecting a different outcome. FiveAPI is not an uncensored AI video API.

This note is for developers who need to surface a clear error to their own users instead of treating every failed task as a transient outage.

How the error shows up

Generation is asynchronous. After you POST a task, you get a queued id, then a signed webhook or a poll of GET /v1/tasks/{task_id}. When the policy rejects the job, the task ends as failed and data.error uses the code content_moderation_rejected. The docs say a reason may name the category:

• ip — protected intellectual property
• audio_copyright
• public_figure

The docs mark this error as not retryable. A failed task releases the held credits in full, so you are not charged for the rejected generation. That is not the same thing as a promise that every prompt will run, or that the API has no filter.

What to tell your product

• Map this code to a specific user-facing message, separate from 429, 402 insufficient_credits, or a generic 5xx.
• Do not automatically recreate the task. Check error.retryable first; for this code it is no.
• Do not advertise the integration as uncensored, unfiltered, or unlimited. None of those claims appear in the public docs.

Account review, prepaid credits, and this policy all sit in front of any production traffic. Start from the docs on FiveAPI's video API rather than from third-party “uncensored” roundups.

Short Q&A

Does a 4xx at create time cost credits? No. Validation and URL-policy rejections happen before a hold.

Can I turn the policy off with a flag? The public docs do not describe a switch to disable content moderation.

— fiveapi.ai notes, 2026-11-13