Ridimensionare un'immagine
Invia un job di ridimensionamento — un’immagine sorgente verso un nuovo rapporto (outpainting lato server).
image sorgente verso un nuovo aspect_ratio. Il ridimensionamento
è un outpainting lato server: il backend renderizza la composizione e la maschera
dalla tua sorgente al rapporto target e riempie la nuova tela esposta con
un’estensione in tinta con lo stile. La chiamata restituisce 202 Accepted con
un id del job; interroga
GET /images/resizes/{id} per il risultato.
L’image prende esattamente uno tra image_id, url o base64 + mime_type.
Richiede lo scope images.transform.
Esempio: una sorgente per modalità
202 è l’handle del job asincrono:
aspect_ratio è obbligatorio e uno tra 21:9, 16:9, 3:2, 4:3, 5:4,
1:1, 4:5, 3:4, 2:3, 9:16. resolution (1K predefinito, 2K, 4K) è
metadato del provider che scala i credits — la tela viene sempre renderizzata con
un bordo massimo di 1024px. num_outputs (1–4) è 1 per impostazione
predefinita e ogni output viene addebitato. prompt è una guida facoltativa per
l’area appena generata (validata se non vuota). placement posiziona la sorgente
sulla tela target: gravity è uno tra center (predefinito), top, bottom,
left, right, top_left, top_right, bottom_left, bottom_right; scale è
in (0, 1] (predefinito 1.0 = contain-fit massimo).aspect_ratio + placement richiesti non
lasciano (quasi) alcuna nuova area da generare — ad es. la sorgente corrisponde già
al rapporto target a scale = 1 — e non viene fornito alcun prompt, il job salta
il modello, restituisce la composizione appiattita e rimborsa gli output non
utilizzati. Si completes comunque.Credits
Ogni output costa5 credits a 1K, con scalatura in base alla risoluzione
(1K ×1, 2K ×2, 4K ×4) e moltiplicato per num_outputs. Vedi
Prezzi.
Errori
Autorizzazioni
Organization API key as a bearer token: Authorization: Bearer samsa_sk_....
Corpo
POST /images/resizes body (SAM-818 / S8.6 — ADR §8, §10).
Resize = server-side outpaint: the backend renders the composition + mask from
your source at the target aspect_ratio and fills the newly exposed canvas
with a style-matched extension. The source is exactly one of image_id (an
image in your organization's context), an https url, or base64+mime_type.
aspect_ratio is REQUIRED (validated against the resize engine's supported
list). num_outputs defaults to 1; each output is billed at
5 x resolution_multiplier credits (1K:1x, 2K:2x, 4K:4x).
Empty-mask no-op: when the requested aspect_ratio + placement leave (almost)
no new area to generate (e.g. the source already matches the target ratio at
scale=1) and no prompt is given, the job SKIPS the model, returns the
flattened composition, and REFUNDS the unused outputs — it still completes.
The source image: exactly one of image_id, an https url, or base64+mime_type. The source raster must be at most 33,554,432 pixels (32 MP, width x height) — a larger source returns 422 with param: image before any rendering. The composition canvas is at most 1024px per edge, so higher-resolution sources gain no output detail.
Target aspect ratio (REQUIRED) — one of: 21:9, 16:9, 3:2, 4:3, 5:4, 1:1, 4:5, 3:4, 2:3, 9:16.
"16:9"
Provider resolution tier — 1K (default), 2K, or 4K. The canvas is always rendered at a 1024px max edge (per S8.5); the tier is provider metadata that scales credits 1K:1x, 2K:2x, 4K:4x per output.
"1K"
Number of images to generate (1-4). Defaults to 1; each output is billed.
1 <= x <= 41
Optional instruction for the newly generated area. When non-empty it runs the app's prompt validation (rejects empty / malformed / policy-violating prompts with a 422).
"extend the beach and the ocean horizon naturally"
Optional placement of the source on the target canvas (gravity + scale). Defaults to centered, maximum contain-fit.
Optional https webhook notified once on terminal status (signed per the webhook signature scheme; see the webhooks docs).
"https://example.com/webhooks/samsa"
Risposta
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.
The job id — poll the op's GET .../{id} endpoint.
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).
pending, processing, completed, failed, cancelled "pending"
Credits this job is expected to cost — 0 on a cache-hit completed response.
5

