Cancel Order

Template UUID. Put it into template_id when creating an order.

ID of the template owner.

Short public identifier used for sharing. null on a template that was never shared.

Template name — for humans only; it does not affect generation.

Code of the service whose schema validates config: elevenlabs, lumimg, and so on.

The template’s service for reference: name and pricing, without configuration schemas. null means no service with that code exists any more.

Generation settings: voice, model, speed and so on — the set of keys is defined by the service. Look up allowed values in GET /templates/config-options?service=<code>; anything outside the schema is rejected with 422. Inside an order (template in GET /orders/{order}) this is the order’s own settings — the snapshot taken at creation with config_override applied, not the template’s current configuration (for orders created before late September 2026 — the current template configuration with config_override).

Whether the template is published in the shared catalogue.

UUID of the folder holding the template, or null for the root. The folder tree is visible in GET /templates/browse.

When the template was created, ISO 8601.

When the template last changed, ISO 8601.

Internal identifier of the asset.

Asset code: LUMC is the internal currency, TOKEN the generation tokens.

Kind of asset: money or consumable units. It decides whether an amount counts as a payment or as quota consumption.

Number of decimal places. The load-bearing field: every integer amount in this asset is divided by 10^precision to obtain the real value. Do not assume the divisor is 100.

Display name of the asset, in the account language.

When the asset was retired, ISO 8601. null while it is in use.

When the asset was created, ISO 8601.

When the asset last changed, ISO 8601.

Zero-based index of the paragraph.

How many chunks the paragraph was split into.

How many of the paragraph’s chunks are already finished.

Aggregate status of the paragraph: derived from its chunks’ statuses rather than stored separately. It uses its own, shorter vocabulary: pending, in_progress, failed, completed — a chunk blocked by moderation also reads as failed. Only the original chunks count, so a successful retry of a failed fragment does NOT change the paragraph status: check the fragment itself in items[].

Paragraph completion percentage, 0–100.

The whole paragraph stitched into one audio file: an absolute path, or a structure carrying path and size. Download it via POST /storage/url, same as the other order files. null means two different things depending on chunks_count: with chunks_count = 1 the paragraph has no file of its own and never will — the paragraph is that single fragment, so take its result_file from items[] under the same paragraph_index; with chunks_count > 1 the stitch has not happened yet — a multi-chunk paragraph gets its file ONLY after stitching, never in advance.

Chunk UUID. Use it in /orders/{order}/items/{item}/… paths.

UUID of the order this chunk belongs to.

What the record is: chunk is an original fragment, retry a free re-run of a failed one, regeneration a paid redo of a finished one.

Retries and regenerations are separate records sharing the same chunk_index: the full attempt history is kept, and the last one is what the result plays.

Zero-based position of the fragment within the order. It defines the order in which the final file is assembled.

The paragraph this fragment belongs to — filled in only for the original fragments of a paragraph-mode order. It is null both in ordinary mode and on retry or regeneration records: those carry no paragraph link of their own and inherit it from the parent fragment via parent_item_id. The mode is switched on by the generation_mode key in the order's config_override.

UUID of the source chunk — present on retry and regeneration records. null on an original chunk.

Length of the text the fragment was created with. It is the ceiling for text in regenerate.

Length of the fragment’s current text: after a regeneration it differs from original_text_length.

Cost of the fragment in tokens — not money. The monetary amount lives on the order itself, in its own price_units field (LMC there, tokens here; the names match, the units do not).

How many tokens were actually charged for this fragment. Zero while the fragment is unfinished.

How many tokens are still reserved for the fragment. Drops to zero once the fragment finishes or is cancelled.

Fragment state: pending waits for a worker, processing is in flight, completed is done, failed hit a technical error, and policy_flagged was rejected by the content policy.

The difference between the last two dictates the fix: failed is cured by retrying as is, whereas policy_flagged requires rewording — retrying the same text is rejected again.

The finished fragment’s file: an absolute path, or a structure carrying path and size. Download it via POST /storage/url, same as order files. null until the fragment is ready.

Duration of the produced audio in milliseconds — the length of the recording, not the generation time. null for non-audio tasks.

Attempt number for this fragment, starting at 1. It grows with every retry.

Whether a free retry is allowed right now. It already accounts for status, task type and exhausted attempts, so you need not re-check the conditions.

Whether a paid regeneration is allowed right now. Available for finished fragments only.

When the fragment was created, ISO 8601.

When the fragment last changed, ISO 8601.

Machine-readable failure reason — present only on failed and policy_flagged. Everything else gets null.