Flux 3 Image
Flux · Image · Text → Image
Generate and edit images with up to 10 references — multi-reference composition, precise local edits and text rendering, natively up to 4K.
flux-3-imageWorkflow: bfl/v1/flux-3-imageOverview
Alongside the unified model APIs, we expose compatibility APIs that take each vendor's original parameters exactly as the vendor defines them — nothing renamed, nothing reshaped on the way through.
That makes them the shortest path onto Picsart if you already work with the vendor directly: the request bodies you've already written keep working as they are. You keep their parameter names and defaults, and you get the vendor's full parameter set rather than the subset that is shared across every model.
The cost is that a request is written for one vendor — switching models later means rewriting it, and results come back in the vendor's own shape. When you'd rather write once and change models freely, use the unified API.
Make a request
Call the workflow with ai.apis.run() in TypeScript, or hit /workflows/{workflow}/execute directly — params is passed through untouched either way.
These endpoints are addressed by workflow name rather than model id: the one in this model's header, since one model runs as one workflow. Authentication is unchanged — your Picsart API key as a bearer token (see Authentication).
import { createClient, ApiRunMode } from '@picsart/ai-sdk';
const ai = createClient({
apiKey: process.env.PICSART_API_KEY,
apiUrl: 'https://api.picsart.com',
});
// Calls the 'bfl/v1/flux-3-image' workflow directly — params are sent as-is.
const { result, usage } = await ai.apis.run('bfl/v1/flux-3-image', {
prompt: "A serene mountain lake at golden hour, ultra detailed"
}, {
mode: ApiRunMode.SYNC,
});
console.log(result); // workflow-specific output
console.log(usage?.credits); // credits chargedParameters
8 parameters, sent inside params. These are the vendor's own names, so they line up one-for-one with the vendor's documentation. Required ones must be supplied; the rest fall back to their defaults.
| Parameter | Type | Required | Default | Details |
|---|---|---|---|---|
promptText description of the image to generate, or of the edit to apply to `imageUrls` | string | yes | — | — |
imageUrlsReference images the prompt edits or draws from, up to 10. Passing any switches the request to editing mode. Each source must be at least 256x256; larger references are downscaled on the Picsart CDN before they reach the vendor, which rejects anything above 4MP. | string[] | no | — | e.g. ["https://example.com/product.jpg","https://example.com/scene.jpg"] |
aspectRatioAspect ratio of the output. With `auto` (the default) the ratio follows the first reference image, or the prompt when there is none. | string | no | auto | auto21:92:116:93:27:54:35:41:14:53:45:72:39:169:211:2 |
resolutionOutput resolution tier. `4k` is generated natively and takes several minutes per image. | string | no | 1k | 768sq1k1.5k2k4k |
countNumber of images to generate. The vendor has no batch endpoint, so each one is a separate FLUX job and cost scales with it. | number | no | 1 | 1–10 |
safetyToleranceModeration tolerance for inputs and outputs, 0 (strictest) to 4. | number | no | 2 | 0–4 |
versionEndpoint version. Only `latest` is accepted today; dated release tags will be added as the vendor publishes them. Left unset, the vendor default (`latest`) applies. | string | no | — | — |
optionsOptions controlling safety checks and drive integration | object | no | — | — |
└ safety_checksSafety check settings | object | no | — | — |
└ enabledWhether to run content moderation. Defaults to true. | boolean | no | — | — |
└ driveSave result to Picsart Drive | object | no | — | — |
└ nameFile name in Picsart Drive | string | yes | — | — |
└ attributesCustom attributes to attach to the file | object | no | — | — |
└ folderTarget folder in Picsart Drive | object | no | — | — |
└ inputs_transformationInput transformation settings | object | no | — | — |
└ downscale_oversized_imagesWhether to downscale oversized input images. Defaults to false. | boolean | no | — | — |
Response
Over HTTP the output arrives inside a status envelope, at response.result. ai.apis.run() unwraps that envelope for you and resolves to { result, usage } instead. Either way the resultitself is the vendor's own shape.
{
"result": {
"items": [
{
"url": "https://cdn.picsart.com/…/result.jpg",
"mimeType": "image/jpeg",
"driveFile": {}
}
]
},
"usage": {
"credits": 1
}
}