Skip to main content
POST
Save a reviewing character (move to ready)
POST /v1/characters/{id}/save moves a reviewing character to ready, cleans up temporary upload bytes from the synthesis pipeline, and makes the character referenceable via character_id on POST /v1/images or POST /v1/videos. This endpoint costs no credits and dispatches no inference — it is purely a state transition.

When to use

  • A build without auto_save: true, or a resynthesize, left the character at status: reviewing and you’ve inspected refs[] — the character’s eight named views (head_front, upper_front, lower_front, upper_back, lower_back, full_left, full_front, full_right) look right and you’re ready to use the character.
  • Those are the only two cases. Both create flows advance to ready on their own, so a character you just created never needs a save — calling it on one returns 200 with the status unchanged. Pass auto_save: true on a build and it lands at ready directly, so you never call this route on the builder path either.
If the refs don’t look right, call POST /v1/characters/{id}/refs/{view}/regenerate (one view) or POST /v1/characters/{id}/resynthesize (every generated view) instead. To discard, call DELETE /v1/characters/{id}.

Examples

Limits

  • Rate limit: bucket characters_post — 30 requests/min sustained, 60 burst per team.

Errors

Common pitfalls

  • Save is idempotent on already-ready characters — calling it twice returns 200 both times with status: ready unchanged. Use this property to retry confidently.
  • A synthesizing character returns 400 — don’t call save until you’ve polled and seen status: reviewing.
  • After save, the character cannot be returned to reviewing. To retry refs, call regenerate-view (a single view) or resynthesize (every generated view).

Authorizations

X-Api-Key
string
header
required

Your team API key (starts with al_live_).

Headers

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"

Response

Character saved

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"