Recraft AI Recraft V4 Pro Create Style API Documentation
Playground
Try it on WaveSpeedAI!Recraft V4 Pro Create Style creates a reusable Recraft style ID from reference images, enabling consistent visual style control for image generation, brand assets, design systems, marketing visuals, and creative production workflows. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.
Features
Recraft V4 Pro Create Style creates a reusable Pro style from reference images. Upload 1 to 10 images, choose a base style, and control how closely the generated style should match the references.
Why Choose This?
-
Reusable Pro style creation
Create a reusable style ID for Recraft V4 Style Pro generation workflows. -
Reference-based style capture
Use uploaded images to define the visual style, mood, composition, and design language. -
Multi-image input
Upload 1 to 10 reference images for stronger and more consistent style extraction. -
Style match control
Chooseprecisefor closer reference matching orflexiblefor broader interpretation. -
Base style selection
Useanyfor general styles orvector_illustrationfor vector-style references.
Parameters
| Parameter | Required | Description |
|---|---|---|
| images | Yes | Reference images used to create the reusable style. Supports 1 to 10 image URLs. |
| base_style | No | Base style type: any or vector_illustration. Default: any. |
| match | No | Style match mode: precise or flexible. Default: precise. |
How to Use
- Upload reference images — Provide 1 to 10 images that represent the style you want to capture.
- Choose base style — Use
anyfor general style creation orvector_illustrationfor vector-style output. - Set match mode — Use
precisefor closer style matching orflexiblefor broader interpretation. - Submit — Generate a reusable Pro style result.
Pricing
Pricing is fixed at $0.0055 per request.
| Output | Cost |
|---|---|
| One Pro style creation request | $0.0055 |
images, base_style, and match do not add separate charges.
Best Use Cases
- Pro style creation — Create reusable style IDs for Recraft V4 Style Pro workflows.
- Brand visual systems — Capture brand visuals, campaign looks, or design directions from references.
- Illustration style matching — Build reusable styles from vector or illustration references.
- Creative consistency — Reuse the same style across later image or vector generation tasks.
- Production workflows — Standardize style before generating larger creative batches.
Pro Tips
- Use visually consistent reference images for stronger style extraction.
- Provide multiple references when the style is complex or needs better definition.
- Use
precisewhen the generated style should closely follow the references. - Use
flexiblewhen you want the model to generalize the style more broadly. - Use
vector_illustrationwhen the references are clearly vector-style or flat illustration assets.
Notes
- The generated
style_idmust be used with the matching model version. - Use a Recraft V4 Style Pro
style_idonly withrecraft-v4-style-promodels. - Use a standard Recraft V4
style_idonly withrecraft-v4-stylemodels. - Do not mix standard and Pro style IDs across model versions.
Related Models
- Recraft V4 Style Text-to-Image — Generate images using a reusable standard Recraft V4 style.
- Recraft V4 Style Text-to-Vector — Generate vector graphics using a reusable standard Recraft V4 style.
- Recraft V4 Style Pro Text-to-Image — Generate images using a reusable Recraft V4 Style Pro style.
- Recraft V4 Style Pro Text-to-Vector — Generate vector graphics using a reusable Recraft V4 Style Pro style.
Authentication
For authentication details, please refer to the Authentication Guide.
API Endpoints
Submit Task & Query Result
set -euo pipefail
export WAVESPEED_API_KEY="your-api-key"
REQUEST_BODY=$(cat <<'JSON'
{
"images": [
"https://interactive-examples.mdn.mozilla.net/media/cc0-images/painted-hand-298-332.jpg"
],
"base_style": "any",
"match": "precise"
}
JSON
)
# 1. Submit the prediction.
SUBMIT_RESPONSE=$(curl --silent --show-error --fail-with-body \
-X POST "https://api.wavespeed.ai/api/v3/recraft-ai/recraft-v4-pro/create-style" \
-H "Authorization: Bearer ${WAVESPEED_API_KEY}" \
-H "Content-Type: application/json" \
-d "${REQUEST_BODY}")
TASK=$(printf '%s' "${SUBMIT_RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
PREDICTION_ID=$(printf '%s' "${TASK}" | jq -r '.id // empty')
if [ -z "${PREDICTION_ID}" ]; then
printf 'Submission response did not contain a prediction id
' >&2
exit 1
fi
RESULT_URL="https://api.wavespeed.ai/api/v3/predictions/${PREDICTION_ID}/result"
# 2. Poll until the prediction finishes.
while true; do
RESPONSE=$(curl --silent --show-error --fail-with-body \
"${RESULT_URL}" \
-H "Authorization: Bearer ${WAVESPEED_API_KEY}")
RESULT=$(printf '%s' "${RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
STATUS=$(printf '%s' "${RESULT}" | jq -r '.status // empty')
case "${STATUS}" in
completed) printf '%s\n' "${RESULT}" | jq '.outputs'; break ;;
failed|cancelled|timeout|deleted) printf '%s\n' "${RESULT}" | jq . >&2; exit 1 ;;
*) sleep 2 ;;
esac
doneParameters
Task Submission Parameters
Request Parameters
| Parameter | Type | Required | Default | Range | Description |
|---|---|---|---|---|---|
| images | array<string> | Yes | - | 1 ~ 10 items | Upload 1 to 10 images used to create the reusable style. |
| base_style | string | No | any | any, vector_illustration | - |
| match | string | No | precise | precise, flexible | - |
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data.id | string | Unique identifier for the prediction, Task Id |
| data.model | string | Model ID used for the prediction |
| data.outputs | array | Output values, usually URL strings; some models return text strings or structured result objects (empty when status is not completed) |
| data.urls | object | Object containing related API endpoints |
| data.status | string | Task status. completed is successful; failed, cancelled, timeout, and deleted are failure terminal statuses. |
| data.created_at | string | ISO timestamp of when the request was created (e.g., “2023-04-01T12:34:56.789Z”) |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |
Result Request Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| id | string | Yes | - | Task ID |
Result Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data | object | The prediction data object containing all details |
| data.id | string | Unique identifier for the prediction |
| data.model | string | Model ID used for the prediction |
| data.outputs | array<string | object> | Array of generated outputs (empty when status is not completed). Items are usually URL strings, but may be text strings or structured result objects, depending on the model. |
| data.urls | object | Object containing related API endpoints |
| data.status | string | Status: completed is successful; failed, cancelled, timeout, and deleted are failure terminal statuses |
| data.created_at | string | ISO timestamp of when the request was created |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |