Supprimer un arrière-plan
Soumets un job de suppression d’arrière-plan — une image source — et récupère un PNG transparent.
image source, produisant un PNG transparent. L’appel
renvoie 202 Accepted avec un id de job ; interroge
GET /images/background-removals/{id}
pour le résultat. L’image prend exactement un de image_id, url ou
base64 + mime_type. Il n’y a aucun paramètre de modèle — v1 utilise le modèle
de suppression d’arrière-plan par défaut. Requiert le scope images.transform.
Exemple : une source par mode
pending :
image_id que tu possèdes et qu’un résultat avec arrière-plan supprimé existe déjà
pour lui, la soumission renvoie immédiatement 202 avec status: "completed"
et estimated_credits: 0 — aucun nouveau job n’est mis en file et le plafond de
concurrence de ton organisation n’est pas consommé. Tout autre cas (une source
https url/base64 ou un image_id possédé sans résultat prêt) est le chemin
facturé normal ci-dessus.Erreurs
Autorisations
Organization API key as a bearer token: Authorization: Bearer samsa_sk_....
Corps
POST /images/background-removals body (SAM-820 / S8.8 — ADR §7, §8, §10).
Remove the background from ONE source image, producing a transparent PNG.
The source is exactly one of image_id (an image in your organization's
context), an https url, or base64+mime_type. There is NO model
parameter — v1 uses the default background-removal model.
Cost = 1 credit on a miss; 0 on a cache HIT. When the source is an
image_id you own and a background-removed result already exists for it, the
submit returns 202 with status: "completed" and estimated_credits: 0
immediately (no new job is queued and the org's concurrency cap is not
consumed). Every other case (an https url/base64 source, or an owned
image_id with no ready result) is the normal charged path: 202 with
status: "pending" and estimated_credits: 1.
The source image: exactly one of image_id, an https url, or base64+mime_type.
Optional https webhook notified once on terminal status (signed per the webhook signature scheme; see the webhooks docs). On a cache hit the completed event fires immediately.
"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.
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

