Mango9 Create / Developers & API

Build the workflow behind the creative.

Connect your app to projects, generation, editing, and delivery. Use Create as the creative production workspace behind your own tools.

Start creating Log in to Create
Open the live OpenAPI reference
Your app + Create API
01Create a project
02Upload or generate media
03Edit, preview, and render
04Receive completion · deliver

HTTPS · JSON · Bearer authentication

What you can build

From one request to a production workflow.

Build campaign tools, media utilities, or internal production systems. The API exposes specific operations you can combine with your own approval and delivery process.

Projects, assets & brands

Create projects and scenes, upload media, and attach reusable brand assets. Use resumable uploads for larger files and authenticated content endpoints for retrieval.

  • POST /projects
  • POST /uploads
  • GET /brands/{id}/assets

Model-driven generation

Discover available models, required inputs, and current account prices. Submit image, video, or audio work and poll the accepted job for completed asset IDs.

  • GET /models
  • POST /generations
  • GET /generations/{id}

A programmable timeline

Read the timeline and apply commands for clips, tracks, audio, captions, effects, and transitions. Use the editor catalog to explore available tools and settings.

  • GET /editor/catalog
  • GET /projects/{id}/editor/timeline
  • POST /projects/{id}/editor/commands

Brand templates & variants

Publish immutable template versions with typed slots. Apply variations to prepared editor projects, validate with a dry run, and keep each variant's production work separate.

  • POST /templates
  • POST /templates/{templateId}/variants
  • POST /projects/{id}/editor/batches

Transcription & media review

Request word-timed transcripts and caption files. Review frames, sound, motion, and captions; use completed transcripts for English translations or proposed interview edits.

  • POST /assets/{id}/transcriptions
  • POST /assets/{id}/reviews
  • POST /speech-edits

Rendering, finishing & delivery

Render a preview or full timeline, normalize audio into a new derivative, and retrieve the finished files. Connect supported completion events to your own system.

  • POST /projects/{id}/editor/render
  • POST /assets/{id}/finishes
  • POST /webhooks

Your first request

A project is a good place to start.

Set your API key as a server environment variable, then create a named project. The response includes the project and its scene IDs, ready for the next step.

  • Base URL: https://create.mango9.com/api/v1
  • Success: data plus meta.requestId
  • Errors: inspect error.code and error.message
Read the integration guide 
# Run on your server with CREATE_API_KEY in the environment.
curl --fail-with-body \
  https://create.mango9.com/api/v1/projects \
  -H "Authorization: Bearer $CREATE_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{"name":"Spring launch","aspectRatio":"9:16"}'

Creates one empty project. No generation is submitted.

01

Authenticate on your backend

Create an API key in the signed-in app. Send Authorization: Bearer with API requests. Keys have full access to the Create operations available to their account and projects; keep them out of browser code.

02

Prepare a project and media

Create a project, keep its scene IDs, and upload or attach the source assets. Discover current models and pricing before requesting generation. API requests use the account's existing balance and permissions.

03

Submit work and track it

For generation and editor operations that require it, supply an Idempotency-Key UUID. Poll the returned job or status URL. Reuse the original key when retrying the same request to resume the job without duplicating work.

04

Review and deliver the result

Check completed results, render a preview when useful, and download the final asset. Your application can use supported webhooks for completion notifications and revocable links when recipients cannot send authentication headers.

The same creative workspace

Automate the repeatable parts. Review the result.

Use code to prepare material and apply repeatable edits. The native editor gives your team a place to inspect the timeline and refine the creative decisions.

  • Start or reconnect an editor session for a project.
  • Read its revision before applying a command.
  • Preview a range or render the complete timeline.

The interactive editor URL requires a Central browser session with project edit access. An API key is for your integration; it does not sign a person into the editor.

Explore the editor
Glow's timeline in the interactive Create editor
Glow's timeline in the interactive Create editorGlow project · Mango9 Create

Ideas for your integration

Make Create part of the way you work.

A campaign production tool

Prepare brand assets, apply a versioned template to separate projects, review previews, and deliver approved variations to your own content system.

Start building your workflow

An interview preparation workflow

Upload recorded media, request a transcription, and use a speech-edit job to propose cuts or English caption translations for human review.

Start building your workflow

A media review and delivery service

Request audiovisual checks, inspect the evidence, render the final edit, and send a revocable asset link through your existing customer workflow.

Start building your workflow

Production details

Authentication, retries, and delivery.

Use the live OpenAPI schema for request bodies, response types, and limits.

How do authentication and API keys work?

Create and revoke keys from a Central-authenticated app session. Current keys have full account/project access, expiry of 1–90 days, and a limit of 120 requests per minute per key. Use a server integration; cross-origin browser cookie access is not supported.

How should I handle retries and concurrent edits?

Reuse the original idempotency key for the same supported request. Changed inputs need a new key. Timeline commands also require the current revision; a conflict requires reading the latest state and reviewing your intended edit. Respect Retry-After on 429 and 503 responses.

Which completion events have webhooks?

Supported events are production.completed, production.failed, production.cancelled, review.completed, review.failed, review.cancelled, and render.completed. Generation jobs use polling endpoint to track progress and retrieve completed results.

How do I verify a webhook?

Verify HMAC-SHA256 of X-Mango9-Timestamp + a period + the exact raw request body using the endpoint's signing secret. Compare against the v1 signature in X-Mango9-Signature, reject timestamps outside five minutes, and deduplicate body.id. Delivery is at least once.

Does a speech-edit plan change the timeline?

No. It proposes edits or returns English caption translations from completed transcription reviews. Review the result before applying separate editor commands. Generation and text work use the existing customer wallet.

How do files reach another system?

Download completed assets with authenticated content endpoints. For recipients that cannot send an Authorization header, create a delivery link and revoke it when it is no longer needed. Anyone holding that link can access the asset while the link and source remain valid.

Make your next idea happen

Build your next creative integration.

Already using Builder? Continue with your Mango9 account.

Start creating Log in to Create
Explore the Create guides