Reve 2.1 Edit API Documentation

Reve 2.1 Edit API Documentation

Playground

Reve 2.1 Image Edit transforms existing images with natural-language edit instructions, preserving layout intelligence, accurate text rendering, and fine visual details for posters, ads, product visuals, and typography-rich designs. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.

Features

Reve 2.1 Edit applies natural-language instructions to an existing image. It is designed for precise visual changes, layout-aware recomposition, and detailed image refinement while preserving the parts of the source image that should remain unchanged.

Why Choose This?

• Instruction-based image editing
  Edit an existing image by describing the desired change in natural language.

• Precise visual refinement
  Apply focused changes to objects, backgrounds, colors, lighting, layout, or style.

• Preservation-aware editing
  Keep important parts of the original image unchanged while modifying selected details.

• Layout-aware recomposition
  Adjust composition and visual structure while maintaining a coherent final image.

• Flexible output formats
  Export edited images as png, jpeg, or webp.

Parameters

How to Use

1. Upload your image — Provide the source image you want to edit.
2. Write your edit prompt — Describe the desired changes and clearly state what should remain unchanged.
3. Choose aspect ratio — Select an aspect ratio or use auto to let the model choose the best layout.
4. Choose output format — Select png, jpeg, or webp when needed.
5. Submit — Generate the edited image and retrieve the output URL.

Pricing

Best Use Cases

• Background editing — Replace, clean up, or restyle image backgrounds.
• Object changes — Remove, replace, recolor, or refine objects in an image.
• Product image refinement — Improve product visuals for marketing, ecommerce, and presentation.
• Layout adjustments — Recompose images while keeping the main subject and visual intent intact.
• Portrait and scene edits — Adjust style, lighting, mood, or environment in existing images.

Pro Tips

• Describe both the change and the elements that must stay unchanged.
• Use concise, concrete instructions for object removal, replacement, color, lighting, and background edits.
• Use a clear source image with the main subject visible.
• Use png for high-quality general output, jpeg for smaller files, and webp for web-friendly images.

## Authentication

For authentication details, please refer to the [Authentication Guide](/api-authentication).

## API Endpoints

### Submit Task & Query Result

<ApiTabs submitUrl={model.submitUrl} resultUrl={model.resultUrl} payload={model.defaultValues} />

## Parameters

### Task Submission Parameters

#### Request Parameters

<RequestParams params={model.params} />

#### Response Parameters

<SubmitResponse />

#### 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&lt;string \| object&gt; | 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.urls.get | string | URL to poll for the prediction result |
| data.status | string | Status: `created`, `processing`, `completed`, or `failed` |
| 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 |