Building on the Omnira API: from key to first render

The Omnira API gives you the same engine that powers the studio — headless. This walkthrough takes you from a fresh API key to a finished render handled cleanly in production.

Authenticate

Create a key in the dashboard and send it as a Bearer token on every request. Keys are scoped, metered, and can carry their own spend caps — so a leaked test key can never drain your whole balance.

Queue a job

POST to /v1/video/generate with your model, modality, and prompt. The response comes back immediately with a job id, a queued status, and the exact credit estimate — you are not blocked while the GPU works.

Subscribe to events

Rather than polling, register a webhook and let Omnira push job.progress and job.completed to your server. Verify the X-Omnira-Signature header against your signing secret so you can trust every payload.

• job.completed — output is ready at a signed URL
• job.failed — structured reason, no credits charged
• job.cancelled — you or the system stopped it
• queue.position — live position while waiting

Handle the output

Completed jobs return a signed, time-limited CDN URL. Download and re-host it, or stream it straight to your user. Because every step is idempotent, retries are safe — the same input never bills you twice.

“Treat generations like any async job: queue, subscribe, verify, store. The API is built to make that boring — in the best way.”