Skip to main content
POST
Generate creative variations of an image
Génère des variations créatives d’une image source. L’appel renvoie 202 Accepted avec un id de job ; interroge GET /images/variations/{id} pour le résultat. L’image prend exactement un de image_id, url ou base64 + mime_type. Requiert le scope images.transform.

Exemple : une source par mode

La réponse 202 est le handle de job asynchrone :
202 Accepted
Envoie exactement un mode source dans image. target — ce que les variations peuvent changer — est everything (défaut), person, object ou scene. creativity est subtle ou creative (défaut). variation_instructions (quoi changer) et preservation_instructions (quoi conserver) sont du texte libre optionnel, ≤ 2000 caractères chacun. num_outputs (1 à 4) vaut 1 par défaut et chaque sortie (output) est facturée. Il n’y a pas de paramètre resolution — la résolution de sortie est héritée de la source.

Credits

Chaque sortie (output) coûte 5 credits en 1K, en fonction du palier de résolution de l’image source (1K ×1, 2K ×2, 4K ×4) et multiplié par num_outputs. Voir Tarifs.

Erreurs

Autorisations

Authorization
string
header
requis

Organization API key as a bearer token: Authorization: Bearer samsa_sk_....

Corps

application/json

POST /images/variations body (SAM-816 / S8.4 — ADR §8, §10).

Generate creative variations of ONE source image (the app's Gemini 3 Pro variations flow). The source is exactly one of image_id (an image in your organization's context), an https url, or base64+mime_type. The output resolution is inherited from the source (there is no resolution param); each output is billed at 5 x resolution_multiplier credits (1K:1x, 2K:2x, 4K:4x) where the multiplier is the source image's resolution tier. target and creativity are lowercase public aliases of the internal Gemini variation controls; num_outputs defaults to 1 (the app default is 4).

image
PublicImageEditSource · object
requis

The source image: exactly one of image_id, url, or base64+mime_type.

target
enum<string>
défaut:everything

What the variations may change: everything (default), person, object, or scene.

Options disponibles:
everything,
person,
object,
scene
Exemple:

"everything"

creativity
enum<string>
défaut:creative

How far the variations may deviate from the source: subtle or creative (default).

Options disponibles:
subtle,
creative
Exemple:

"creative"

variation_instructions
string | null

Optional free-text guidance for WHAT to change (<= 2000 chars).

Maximum string length: 2000
Exemple:

"Try different background colors and lighting"

preservation_instructions
string | null

Optional free-text guidance for WHAT to keep (<= 2000 chars).

Maximum string length: 2000
Exemple:

"Keep the product label and shape unchanged"

num_outputs
integer
défaut:1

Number of variations to generate (1-4). Defaults to 1 (the app default is 4); each output is billed.

Plage requise: 1 <= x <= 4
Exemple:

1

webhook_url
string | null

Optional https webhook notified once on terminal status (signed per the webhook signature scheme; see the webhooks docs).

Exemple:

"https://example.com/webhooks/samsa"

Réponse

Successful Response

Shared 202 body for the transform-op submits (SAM-813 / S8 wave).

Every POST /images/<op> returns the async job handle {id, status, estimated_credits}. The initial status is pending (the job is queued), with ONE exception: background-removals and vectorizations answer an owned-image_id cache hit (a ready result already exists for that image) with status: "completed" and estimated_credits: 0 — no new job is queued, the completed webhook event is emitted immediately for a supplied webhook_url, and the result is already available from the op's GET .../{id} endpoint. The other transform ops (img2img, variations, resizes, upscales) always start pending.

id
string<uuid>
requis

The job id — poll the op's GET .../{id} endpoint.

status
enum<string>
requis

Initial status: pending (job queued — enter the polling flow), or completed with estimated_credits: 0 when background-removals / vectorizations serve an owned-image cache hit (the result is immediately available).

Options disponibles:
pending,
processing,
completed,
failed,
cancelled
Exemple:

"pending"

estimated_credits
integer
requis

Credits this job is expected to cost — 0 on a cache-hit completed response.

Exemple:

5