Skip to main content
POST
Regenerate a single ref pose (synchronous)
Deprecated body form. Use POST /v1/characters/{id}/refs/{view}/regenerate, which reaches all eight named views. This route stays supported with no sunset date; its pose field resolves through a fixed alias table:
POST /v1/characters/{id}/refs/regenerate re-runs the synthesize pipeline for one view, leaving the other refs intact. Use it when one reference needs another try and the rest are fine — the pose you send is resolved through the alias table above, so this route can reach four of the eight named views. Every 2xx from this route carries Deprecation: true and a Link header with rel="successor-version" pointing at Regenerate a view, so the migration shows up in your logs. There is no Sunset header: no removal date has been announced. The endpoint returns 200 with the updated character resource (Stripe pattern — the resource exists and this is a state transition, not a new-resource creation). The call is synchronous: it blocks until the new ref is rendered and the response carries the updated character. It does not move the character to status: synthesizing — the status you sent it in (ready or reviewing) is the status it comes back with, so there is nothing to poll. This endpoint costs credits — one generation per call, charged before the render is dispatched. A render takes 60–180 seconds; set a client timeout of at least 300 seconds. Aborting the request client-side neither cancels the render nor refunds the credits. Read build.per_view_credits on any character response for the current per-view price — one call costs exactly that — if you need a budget guardrail in your UI.

When to use

  • One synthesized ref came back wrong and you want to fix only that one.
  • A failed regen needs another attempt without touching other poses.
To reach upper_front, lower_front, lower_back, full_right or any view by name, use POST /v1/characters/{id}/refs/{view}/regenerate. To regenerate the whole set, call POST /v1/characters/{id}/resynthesize instead.

Body

Examples

Limits

  • Rate limit: bucket characters_synthesize — 15 requests/min sustained, 30 burst per team. Shared across POST /v1/characters, POST /v1/characters/{id}/refs/regenerate, POST /v1/characters/{id}/refs/{view}/regenerate, POST /v1/characters/{id}/resynthesize and POST /v1/characters/{id}/build — five routes, one bucket.
  • 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 a paid generation, so a network retry without a key can double-charge.

Errors

Common pitfalls

  • The body pose enum accepts portrait, front, side, back. other and anything else is 400 invalid_format, and pose is resolved before the character is looked up — an unknown pose is a 400 even for an id that does not exist.
  • The character’s status does not change. The call blocks until the new ref exists and returns the updated character, so there is nothing to poll afterwards.
  • Regenerating from ready is allowed — existing generations that already reference the old ref are unaffected; only future requests pick up the new reference.
  • A view holding a photo you uploaded cannot be regenerated through either form of this route — it returns 400 reference_uploaded. Replace it with PUT /v1/characters/{id}/refs/{view}, or remove it from a draft and let a build render it. Read views[].status to tell the two apart.

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). Omit the header to receive the platform default, currently 2026-08-26.

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

"2026-08-26"

Path Parameters

id
string
required

Opaque character ID

Example:

"char_01HXMQ7Z3K8Y2NABCDEFGHJKMR"

Body

application/json
pose
enum<string>
required
deprecated

DEPRECATED body form — use POST /v1/characters/{id}/refs/{view}/regenerate, which reaches all eight views. This field keeps its original five values and resolves through a fixed alias table: portraithead_front, frontfull_front, sidefull_left, backupper_back. other is rejected with 400 invalid_format. No sunset date; the route stays supported.

Available options:
portrait,
front,
side,
back,
other
Example:

"front"

prompt_override
string

Optional prompt override for this single pose. Falls back to the character.attributes-derived prompt when omitted.

Example:

"soft studio lighting, neutral background"

Response

Ref pose regenerated; updated character returned

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. draft: references are being assembled; nothing has been charged and the character cannot be used for generation. New lifecycle states may be added in future — treat any status other than ready as "not yet usable". synthesizing: references are being built. ready: usable on POST /v1/images — both create flows advance here on their own. reviewing: reached only after POST /:id/resynthesize or POST /:id/build; call POST /:id/save to return to ready. failed: the build failed; error_message carries the reason and POST /:id/build (builder characters) or POST /:id/resynthesize retries. deleted: soft-deleted (filtered out of the list endpoint).

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

"ready"

nudity
enum<string>
required

What the reference set is rendered as — nude unless you chose clothed, or — when you omitted nudity — your team's default is clothed. An explicit value always wins. Fixed once the references are built.

Available options:
nude,
clothed
Example:

"clothed"

refs
object[]
required

Reference images, one per view the character has. A character built today has eight; an older one can have fewer than eight (typically six, some of the oldest four). Do not assume a count — read views[], the canonical read model for new integrations, or build.missing_views. refs[] lists only the references that exist.

views
object[]
required

One entry per named view, in canonical order — every reference that maps to a named view, keyed by view, plus what is missing or was rejected. A reference from before named views existed (refs[].view is other) appears only in refs[].

build
object
required

What a build would render and cost right now. Always present.

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
string | 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
string | null

Machine-readable failure code from the most recent synthesize/resynthesize attempt. One of synthesis_failed, synthesis_timeout, provider_unavailable — a closed set to switch on, not customer-facing prose. Null when the most recent attempt succeeded (or none has run yet). Set on failed, but NOT failed-exclusive: a failed resynthesize restores the character to its prior working status (reviewing) rather than overwriting a good generation, so a reviewing row can carry a non-null code here — check this field for failure, not status. Cleared on the next resynthesize attempt and on success.

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-08-26"