Resynthesize a character
Re-run the synthesize pipeline to produce a fresh set of refs.
POST /v1/characters/{id}/resynthesize re-runs the synthesize pipeline against the character’s existing attributes to produce a fresh set of ref poses. The endpoint accepts characters in reviewing or failed state.
The call is synchronous: the response returns the updated character with status: reviewing and its fresh refs. Review the refs, then call POST /v1/characters/{id}/save to move the character to ready.
The endpoint returns 200 with the updated character resource (Stripe pattern — the resource exists and this is a state transition).
This endpoint costs credits — same cost as the original synthesize-flow create (4 generations). Estimate via POST /v1/images/estimate on the equivalent prompt if you need a budget guardrail.
Body
Examples
Limits
- Rate limit: bucket
characters_synthesize— 15 requests/min sustained, 30 burst per team. Shared with synthesize-flow create andregenerate-ref. - Idempotency: pass
Idempotency-Key(any opaque value, 1–256 chars). Same key + same body within 24h replays the cached response. Same key + different body returns409 idempotency_key_in_use. See Idempotency.
Idempotency-Key — this endpoint dispatches 4 paid generations,
so a network retry without a key can multiply your bill.Errors
Common pitfalls
resynthesizeis the most expensive character endpoint — always passIdempotency-Keyto avoid double-charges on retry.- Resynthesize works on both
reviewingandfailedcharacters — it’s the primary way to retry a failed synthesis, reusing the character’s storedattributes. If the character’s original uploaded photos have since expired, the call returns422 uploads_expiredinstead (this endpoint doesn’t accept new photos on resynthesize); in that case, delete viaDELETE /v1/characters/{id}and recreate viaPOST /v1/characterswith freshupload_ids. - Resynthesize uses the stored
attributes. If you want to change identity (e.g. differenthair_color), callPATCH /v1/characters/{id}with the new attributes first, then resynthesize.
Authorizations
Your team API key (starts with al_live_).
Headers
Stripe-style idempotency key (1-256 chars). Same key + same canonical-JSON body returns the cached response with Aurous-Idempotent-Replayed: true. Same key against a different route (e.g. previously used on /v1/images) returns 409 invalid_request / idempotency_key_in_use. Replay window is 24 hours. Absent header is treated as non-idempotent (each call processes anew).
Optional API version pin (YYYY-MM-DD). Defaults to your team's pinned version, or the system default 2026-07-16 for unauthenticated requests.
^\d{4}-\d{2}-\d{2}$"2026-07-16"
Path Parameters
Opaque character ID
"char_01HXMQ7Z3K8Y2NABCDEFGHJKMR"
Body
Reserved (no-op today). Resynthesize always regenerates all 4 ref poses in the current API version, so this flag has no effect regardless of its value. It is accepted for forward-compatibility with a future partial-resynthesis mode (regenerate only missing/failed poses).
true
Response
Ref poses resynthesized; updated character returned at status: reviewing
Opaque character ID.
"char_01HXMQ7Z3K8Y2NABCDEFGHJKMR"
Discriminator
character "character"
Display name.
"Aurora the Adventurer"
Lifecycle state. synthesizing: synthesize flow running. reviewing: synthesize completed, awaiting POST /:id/save. ready: usable on POST /v1/images. failed: synthesize failed; use POST /:id/resynthesize to retry. deleted: soft-deleted (filtered out of list endpoint).
synthesizing, reviewing, ready, failed, deleted "ready"
Reference images (typically 4 poses).
Creation timestamp (ISO 8601).
"2026-05-08T10:00:00Z"
Last-update timestamp (ISO 8601).
"2026-05-08T10:00:00Z"
Caller-supplied reference echoed back (the value sent on create). Null if unset.
"bot_8472"
Character attributes. Null when unset.
Error message when status is failed. Null otherwise.
null
API contract version applied at the time this row was minted (D25 — frozen for replay across future version bumps).
"2026-07-16"

