FOR DEVELOPERS

Put the pipeline inside your product.

The JARAI Partner API lets you trigger AI media productions, track them in real time, and pull the finished deliverables — straight from your own application. Identity-first onboarding, scoped keys, a sandbox to build against, and a REST API that does the heavy lifting.

Sign in, create a scoped test key, and make your first call in minutes.

WHAT YOU CAN BUILD

Three calls from idea to finished asset.

JARAI productions are asynchronous — you submit a brief, the pipeline runs its multi-step process, and the result arrives minutes later. Every integration follows the same simple shape.

01

Trigger a production

POST a brief — project type, theme, avatar, options — and get back a production ID. The autonomous pipeline takes it from there.

02

Track it in real time

Poll the status endpoint, or register a webhook and let JARAI call you when the production changes state. No long-polling required.

03

Collect the deliverables

When a production reaches its ready state, pull the packaged assets — video, audio, text, music — with time-limited download URLs.

GET STARTED

From sign-in to first call in minutes.

No registration forms, no waiting for approval. You sign in with your JARAI account and mint a key yourself.

01

Create a scoped key

Sign in to the Studio Console (with your JARAI account — Microsoft, Google, or email), open Settings → API Keys, and create a test key. Choose its scopes — least-privilege by default. The secret is shown once.

02

Make your first call

Send the key in the X-API-Key header, list your accounts, and trigger a production against the sandbox.

03

Go from sandbox to live

When your integration is ready, request a production key and point the same code at your live accounts.

YOUR FIRST CALL

Trigger a production with one request.

Authenticate with your key, post a brief, and poll for the result. Full examples in cURL, Python, and Node.js live in the Developer Portal.

# 1. List the accounts your key can access
curl https://apim-jarai-prd.azure-api.net/v1/accounts \
  -H "X-API-Key: jarai_test_…"

# 2. Trigger a production
curl -X POST https://apim-jarai-prd.azure-api.net/v1/accounts/{accountId}/productions \
  -H "X-API-Key: jarai_test_…" \
  -H "Content-Type: application/json" \
  -d '{ "topic": "Quarterly highlights", "avatarId": "…", "languageId": "…", "countryId": "…" }'

# 3. Poll until the deliverables are ready
curl https://apim-jarai-prd.azure-api.net/v1/productions/{productionId} \
  -H "X-API-Key: jarai_test_…"

BUILT FOR INTEGRATION

Everything you need to ship.

REST API

Predictable JSON over HTTPS, URL-versioned, with structured errors and a correlation ID on every response.

Webhooks

Subscribe to production lifecycle events and get pushed updates instead of polling.

Sandbox

Self-serve test keys scoped to your own sandbox accounts — build and validate before you go live.

Scoped keys

Least-privilege keys you create and revoke yourself. Grant only the scopes an integration needs.

Usage analytics

Per-key request history and usage, so you can see exactly what each integration is doing.

Rate-limit tiers

Clear per-tier budgets with live X-RateLimit headers on every response.

DEVELOPER FAQ

The questions developers ask first.

Sign in to the Studio Console with your JARAI account (Microsoft, Google, or email), open Settings → API Keys, and create a key yourself — it takes seconds. New keys are scoped test keys for the sandbox; you choose exactly which scopes they carry, and the secret is shown only once. There's no registration form and no approval queue.
Yes. Self-serve keys are test keys scoped to your own sandbox accounts, so you can build and validate your integration without touching live distribution or spending beyond your account's allowance. When you're ready, request a production key and point the same code at your live accounts.
Partner API usage draws on the same token allowance and billing as the Console — there's no separate API fee. Productions that would exceed an account's budget are rejected with a clear error rather than partially run, so you're never surprised.
Every key shares a per-partner request budget set by your tier — 10 requests per minute on Free, 60 on Standard, 300 on Enterprise — and every response carries live X-RateLimit headers so you can back off cleanly. Creating more keys doesn't raise the limit; it's shared across your account.

Start building with JARAI.

Sign in, create a scoped test key, and make your first call today.

Open the Developer Portal

Free to start. Build in the sandbox before you go live.