Anbiya Admin

Guided editorial flow for draft import, media registration, and protected publish actions.

Authenticated admin session

All write operations use role/account claims from your admin access token.

Authenticated Role: n/a

Email: n/a

Account ID: n/a

Publishing Wizard

Follow this order every time to avoid publish failures and unsafe production changes.

  1. Configure guardrails Production writes are protected by authenticated role claims, checkpoint, and emergency policy.
  2. Import and save draft Validation catches schema and deterministic key errors before draft persistence.
  3. Register media assets Publish is blocked until referenced image/audio keys exist and are registered.
  4. Confirm publish Publishing is explicit and role-restricted because it changes live library visibility.

Step 1: Configure guardrails

Set operational safety headers first. Production writes are blocked without valid guardrails.

Checkpoint Access token

Step 2: Import and save draft

Import JSON, run strict validation, then save draft. Include variant.thumbnailUrl for library card cover rendering. Draft save forces isPublished=false.

Expected shape: { variant: StoryVariant, pages: StoryPage[] }

Preview: Variant nuh-7-9-en-v1 with 1 page(s).

Validation Draft saved

Step 3: Register media assets

Batch upload supports folder picker and drag/drop. Expected names: p1.webp, p1.mp3, p2.webp, etc. Upload overwrites existing deterministic keys.

Drop files/folder here or select a folder and scan.

Only matching files are queued: p<page>.png/jpg/jpeg/webp/mp3/m4a/wav/webm

Queued: 0 Uploaded: 0 Failed: 0 Duplicates: 0 Unmatched: 0 Missing slots: 2 Existing assets confirmed
PageImageAudioStatus
1missingmissingmissing files
Manual single-file fallback

Step 4: Confirm publish

Publish requires admin role and active production guardrails. This makes the variant live in library queries.

  • Variant ID points to the draft you validated and saved.
  • Variant has a valid public thumbnailUrl for listing cards.
  • Media keys are uploaded or already registered.
  • Backup checkpoint ID matches the current pre-change backup.
Published

API response and diagnostics

Keep this panel open while operating. Errors include request IDs for support and incident tracing.

No response yet. Run a wizard action to see API output.