Vectoriser une image
Soumets un job de vectorisation — une image source vers SVG — et récupère un id de job.
image source en SVG. L’appel renvoie 202 Accepted avec un id
de job ; interroge
GET /images/vectorizations/{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. Requiert le scope
images.transform.
Exemple : une source par mode
svg_acceptance doit être le booléen littéral true à chaque requête :
pending :
image_id que tu possèdes et qu’un résultat vectoriel 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é.Portails d’acceptation
La vectorisation a deux portails de livraison indépendants, tous deux appliqués sans facturation en cas d’échec :svg_acceptancedoit être le booléen littéraltrue. Une valeur manquante,falseou autre est rejetée par422 svg_acceptance_required.- Une acceptation ToS/AUP actuelle et vérifiée côté serveur est également
requise — le flag de la requête n’est jamais considéré comme ce fait. Une
acceptation manquante ou périmée est rejetée par
403 svg_phase1_scope_out_required; accepte les ToS/AUP actuels et réessaie.
Erreurs
Autorisations
Organization API key as a bearer token: Authorization: Bearer samsa_sk_....
Corps
POST /images/vectorizations body (SAM-821 / S8.9 — Art. 50(2) scope-out).
Vectorize ONE source image into an SVG (Recraft; 5 credits flat). 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.
SVG is a documented EU AI Act Art. 50(2) scope-out: an SVG cannot carry a
C2PA manifest or an embedded watermark, so vector outputs are delivered
unsigned. Delivery is therefore gated on svg_acceptance — an explicit
acknowledgment that the SVG is an unsigned, unwatermarked scope-out output.
This acknowledgment is disclosure / audit evidence, NOT a compliance
waiver. svg_acceptance must be the literal boolean true; a missing,
false, or any other value is rejected 422 svg_acceptance_required with no
charge. Delivery ALSO requires a current, server-verified ToS/AUP acceptance
(the request flag is never trusted as that fact); a missing / stale acceptance
is 403 svg_phase1_scope_out_required with no charge.
Cost = 5 credits on a miss; 0 on a cache HIT. When the source is an
image_id you own and a vector 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).
The source image: exactly one of image_id, an https url, or base64+mime_type.
Must be the literal boolean true: an explicit acknowledgment that SVG (vector) output is an EU AI Act Art. 50(2) scope-out delivered UNSIGNED and UNWATERMARKED. This acknowledgment is disclosure / audit evidence, NOT a compliance waiver. Any other value (missing / false) is rejected 422 svg_acceptance_required with no charge.
true
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

