CartVisualCreate account

Recraft V4.1 Rejects My Old Negative Prompt: Which API Fields Must Change?

A Recraft V4.1 request cannot assume older negative_prompt or V3-specific controls are accepted. Audit the actual model schema, remove unsupported fields, and review creative requirements separately.

Published · By CartVisual editorial team

Locate the request-contract mismatch

A hypothetical merchant has a working older image-generation template for cosmetic jars. It contains a product description plus negative_prompt, a curated style, and a text_layout instruction. After changing only the model name to recraftv4_1, the request fails or the expected controls disappear. The first question is not whether the prompt is descriptive enough: the application may be submitting fields the selected model does not support. Save a redacted copy of the actual JSON body, the selected model identifier, and the exact returned validation details. Never infer a particular error message without a real response.

Audit supported and unsupported responsibilities

Recraft V4.1 documents prompt, model, size, output count, style references or a style ID, and a limited set of color controls. It explicitly excludes negative_prompt, curated style, text_layout, artistic_level and no_text. Mark each old field as supported, unsupported, or requiring a new creative decision. Do not silently translate negative_prompt into a guarantee that the model will exclude an object. A prose instruction such as “plain countertop, no additional bottle” can describe the goal, but it does not recreate a documented negative-prompt control.

Make the field audit executable

The V4.1 API model reference is the contract for this example. Audit fields at their documented location; a Studio switch is not a substitute for an API field.

Old request fieldV4.1 decisionRemaining creative responsibility
negative_promptRemove: unsupportedInspect the result for unwanted objects; prose is not an equivalent negative control.
Curated style, text_layoutRemove: unsupportedPlan typography and exact layout in a suitable separate workflow.
controls.artistic_level, controls.no_textRemove: unsupportedApprove the actual art direction and any unwanted lettering.
model, size, nUse supported identifiers and valuesRecord the model, intended frame and output count.
style_id or style_reference_urlsUse the documented style route; do not mix alternativesKeep the style and product reference responsibilities distinct.
controls.colors, controls.background_colorSupported color controlsReview the actual image rather than promising exact product color.

These two fictional bodies isolate one migration error. The first intentionally includes an unsupported field; it is not an approved request. The second removes that field. They are non-executed illustrations, not a claim about a particular returned HTTP error.

Before: incompatible field retained after changing the model.

{
  "model": "recraftv4_1",
  "prompt": "A studio image of one cosmetic jar on a plain countertop",
  "negative_prompt": "additional jars"
}

After: a minimal supported request shape for a concept image.

{
  "model": "recraftv4_1",
  "prompt": "A studio image of one cosmetic jar on a plain countertop",
  "size": "1:1",
  "n": 1
}

Successful validation would establish only that the request is accepted. It would not establish that the resulting jar, label or composition is suitable for the real product. Keep actual request and response records separate from this illustration.

Use a fictional three-row migration ledger

For jar SKU JAR-12, row one records the approved source image and factual constraints: one jar, correct cap, exact label. Row two records the old API-specific exclusions and the destination of each field: unsupported controls are removed from the V4.1 request; the desired clean scene becomes a human-reviewed prompt requirement. Row three records the output review: count the jars, compare cap and label, and inspect the background. The example does not claim a request was executed or that V4.1 reliably obeys every exclusion. If strict label identity is essential, consider a protected-source composite rather than asking a model to reproduce exact print.

Do not borrow Studio UI or another provider’s API rules

A Recraft Studio interface may show a Negative prompt or Avoid text option in a context not identical to the selected API model. The API schema is the authority for the request being sent. The existing Studio-versus-API prompt guide covers Claid’s separate assistance feature; it is not evidence that Recraft copies Studio controls into V4.1. Likewise, model-name parity across tools cannot establish identical request processing. Keep client, model, endpoint and accepted fields in the record.

Decide whether migration is worthwhile

If the campaign depends on a removed control, either revise the workflow around supported V4.1 inputs or evaluate a documented model that retains the required capability. Do not add invented JSON aliases. Release the new request specification only when it matches the chosen model and the merchant has a separate image-fidelity review plan. Keep provider API units distinct from CartVisual credits.

Sources

  • Recraft V4.1 — V4.1 supported parameters and unsupported legacy controls. Source checked 2026-11-16.

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. Illustrative merchant diagnosis only; no provider requests, account operations, image tests, print proofs or integration with CartVisual were executed. Provider capabilities and billing may change.

Related decisions

Explore the AI image remix workflow