Find the repeated operation
A fictional accessories brand generates thirty catalog lifestyle illustrations with the same restrained watercolor treatment. Its integration attaches the same style references to each request. Recraft V4 Styles documents both reference-based style creation and reuse of a returned style identifier. The important question is whether each job intentionally needs a new style or merely needs another image using an approved one. Save a redacted example of the current request structure and separate image-generation cost from style-creation cost.
Create a versioned style asset
Use a documented V4 Styles creation route to define the reference set, then retain the returned creation id, used as style_id, with the campaign brief, reference provenance and chosen model family. Later compatible image-generation requests can pass that ID rather than recreating the reference definition. Recraft documents that a request must supply a style or references and that conflicting style_id plus reference inputs are not a valid combination. Do not copy a style identifier into a model that does not support it; the Flash V2 high-volume route has different style capabilities.
Separate style creation from image generation
The V4 Styles model reference documents the two-stage relationship. The following is a non-executed illustration. Replace the example URL with an authorized reachable image and the placeholder with the actual returned identifier.
Stage one: send the style definition to POST /v1/styles.
{
"model": "recraftv4_styles",
"image_urls": [
"https://example.com/replace-with-owned-style-reference.png"
]
}The creation response returns an id. In this illustrative response, the placeholder is not an actual style.
{
"id": "REPLACE_WITH_RETURNED_STYLE_ID"
}Stage two: send a generation to POST /v1/images/generations, passing that value as style_id and omitting the reference array.
{
"model": "recraftv4_styles",
"prompt": "A catalog illustration of a handbag on a plain display surface",
"style_id": "REPLACE_WITH_RETURNED_STYLE_ID"
}Match the style to the model it was created with. Do not combine style_id and style references in the same request; the documented contract rejects that combination. Reusing the identifier avoids a repeated style-creation event, while each new image remains chargeable.
| Campaign style | Model and style ID | SKU and request | Actual response and download |
|---|---|---|---|
| S1, approved reference revision | recraftv4_styles / actual returned ID | HANDBAG-A / request record | Fill only after a real response and retained download |
| S1, same style reused | Same compatible model / same ID | WALLET-B / separate request record | Record this result independently; do not copy another SKU's approval |
Illustrative batch economics without fake usage
Assume the same style is needed for three groups: handbags, wallets and key cases. Group A creates style S1 from approved mood references. Groups B and C reuse S1 for new product descriptions, retaining their own SKU evidence. The provider documents a separate one-time style-creation charge in addition to per-image charges. The illustrative ledger records one creation event and each generation request separately; no API call, billing transaction or savings measurement was performed. If the art director changes the style references materially, define S2 as a distinct reviewed asset rather than silently overwriting S1 in the campaign register.
Do not confuse a style with a product master
A style ID can guide rendering technique and palette; it does not certify that a generated handbag has the correct buckle or strap. Compare every candidate with the authoritative product source. The existing recurring-model identity guide concerns a different reference responsibility. The reuse-versus-new-generation guide distinguishes existing asset downloads from new charges; reusing a Recraft style does not make later image generation free. A production team should also distinguish a style revision from a product revision. New packaging photography for one SKU does not necessarily justify rebuilding the entire campaign style. Conversely, a new art direction may require a new style identifier even when all product references remain the same. Track those changes in separate columns so a batch can be rerun without silently changing both variables.
Set a durable handoff
Keep the provider model, style ID, approved reference set, style version, image-generation prompt, SKU source, and returned image identifier. Hold when a job mixes incompatible style fields or when the team cannot tell which style version produced an image. The API’s response credits are Recraft units, not CartVisual balances. Temporary returned image URLs should be downloaded according to provider retention guidance. Do not imply a direct CartVisual API integration.