Skip to main content
POST
Remove an image's background (transparent PNG)
Remove the background from one source image, producing a transparent PNG. The call returns 202 Accepted with a job id; poll GET /images/background-removals/{id} for the result. The image takes exactly one of image_id, url, or base64 + mime_type. There is no model parameter — v1 uses the default background-removal model. Requires the images.transform scope.

Example: one source per mode

The normal (charged) path returns a pending job:
202 Accepted
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 your organization’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 above.
202 Accepted (cache hit)

Errors

Authorizations

Authorization
string
header
required

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

Body

application/json

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.

image
PublicImageEditSource · object
required

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

webhook_url
string | null

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.

Example:

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

Response

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>
required

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

status
enum<string>
required

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).

Available options:
pending,
processing,
completed,
failed,
cancelled
Example:

"pending"

estimated_credits
integer
required

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

Example:

5