Skip to main content
POST
Resynthesize all ref poses (synchronous)
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 and regenerate-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 returns 409 idempotency_key_in_use. See Idempotency.
Always pass Idempotency-Key — this endpoint dispatches 4 paid generations, so a network retry without a key can multiply your bill.

Errors

Common pitfalls

  • resynthesize is the most expensive character endpoint — always pass Idempotency-Key to avoid double-charges on retry.
  • Resynthesize works on both reviewing and failed characters — it’s the primary way to retry a failed synthesis, reusing the character’s stored attributes. If the character’s original uploaded photos have since expired, the call returns 422 uploads_expired instead (this endpoint doesn’t accept new photos on resynthesize); in that case, delete via DELETE /v1/characters/{id} and recreate via POST /v1/characters with fresh upload_ids.
  • Resynthesize uses the stored attributes. If you want to change identity (e.g. different hair_color), call PATCH /v1/characters/{id} with the new attributes first, then resynthesize.

Authorizations

X-Api-Key
string
header
required

Your team API key (starts with al_live_).

Headers

Idempotency-Key
string

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

Aurous-Version
string

Optional API version pin (YYYY-MM-DD). Defaults to your team's pinned version, or the system default 2026-07-16 for unauthenticated requests.

Pattern: ^\d{4}-\d{2}-\d{2}$
Example:

"2026-07-16"

Path Parameters

id
string
required

Opaque character ID

Example:

"char_01HXMQ7Z3K8Y2NABCDEFGHJKMR"

Body

application/json
force_all
boolean

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

Example:

true

Response

Ref poses resynthesized; updated character returned at status: reviewing

id
string
required

Opaque character ID.

Example:

"char_01HXMQ7Z3K8Y2NABCDEFGHJKMR"

object
enum<string>
required

Discriminator

Available options:
character
Example:

"character"

name
string
required

Display name.

Example:

"Aurora the Adventurer"

status
enum<string>
required

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

Available options:
synthesizing,
reviewing,
ready,
failed,
deleted
Example:

"ready"

refs
object[]
required

Reference images (typically 4 poses).

created_at
string
required

Creation timestamp (ISO 8601).

Example:

"2026-05-08T10:00:00Z"

updated_at
string
required

Last-update timestamp (ISO 8601).

Example:

"2026-05-08T10:00:00Z"

client_reference_id
object | null

Caller-supplied reference echoed back (the value sent on create). Null if unset.

Example:

"bot_8472"

attributes
object | null

Character attributes. Null when unset.

error_message
object | null

Error message when status is failed. Null otherwise.

Example:

null

aurous_version
string

API contract version applied at the time this row was minted (D25 — frozen for replay across future version bumps).

Example:

"2026-07-16"