Skip to main content
In short: these are moderation errors from the Seedance model itself (BytePlus ModelArk). The model checks both what you send (text, images, video, audio) and what comes out. PolicyViolation means a possible copyright issue: most often the input contains a celebrity or a character from a film, TV series or game. SensitiveContentDetected with no suffix means prohibited content in the prompt, the input files or the finished video. Only changing the input helps; you’re not charged for a rejected task. If the error says may contain real person (PrivacyInformation), that’s a different case — see Seedance: input image may contain real person.

Error codes

In ModelArk, all of them have HTTP status 400. The error messages come from the ModelArk error code table: The message usually ends with Request ID: .... On RuAPI the error arrives in one of two ways:
  • Right at submission. If the reason is copyright or a public figure, you get a 400 response with the code input_copyright_restricted along with a hint about what to do. For other moderation rejections the response is currently generic — upstream task submission failed (HTTP …) — and doesn’t show which code from the table was triggered. Check your prompt and files against the “What you can do” table below.
  • During generation. The task ends with the status failed, with one of the codes from the table in the error field.
Either way, the prepayment is refunded to your balance in full.

Why it happens

  • Public figures. The model doesn’t accept photos of celebrities, influencers or streamers — and auto_create_assets doesn’t help here.
  • Copyrighted characters. Characters from films, TV series, cartoons and games — whether they appear in a picture or are only named in the prompt.
  • Prohibited content. Violence, explicit scenes and other topics banned by the model’s rules — in the prompt, the input files or the output.
  • The check errs on the side of caution. The error says may. Sometimes a perfectly harmless request is rejected too.

What you can do

If your project really needs a public figure and you have their consent, contact support at support@ruapi.ai or on Telegram @RuAPI_Support.

How to use Seedance via RuAPI

1

Sign up

Sign up at www.ruapi.ai — with email, Google or Yandex.
2

Top up

Console → Wallet: USDT or USDC (TRC20 / BEP20 / Polygon; USDT also on TON), from 5 USDT. No USDT yet? Buy it with rubles via SBP (Faster Payments System). Cards from foreign banks (Visa / Mastercard) are accepted too. Video models become available after your first top-up.
3

Key

Console → API Keys → Create API key — you’ll get an sk-... string.
4

Request

Examples for every mode are in the video generation guide. If your code is already written for ModelArk, change the base URL to https://www.ruapi.ai/v1, and swap in your RuAPI key and our model name (for example, doubao-seedance-2.5).

FAQ

No. Only successfully generated videos are billed: if a task is rejected at submission or ends with an error — including OutputVideoSensitiveContentDetected — the prepayment is refunded to your balance in full.
For input errors, no: the same text or file will be rejected again. With OutputVideoSensitiveContentDetected you can try again, but changing the prompt is more reliable.
No. It’s the Seedance model’s own check and can’t be disabled.
No. A RuAPI key is enough: the website and the API work without a VPN.

Next

Video generation: Seedance 2.0 / 2.5

All modes, the ModelArk format, draft mode and prices.

Seedance: real person

Photos and videos of real people, auto_create_assets.