Mango9 Create documentation

API and integrations

Connect projects, media, generation, and exports.

Use the authenticated Create API

Create exposes its public API at https://create.mango9.com/api/v1. It supports project and media workflows, generation jobs, and export operations according to your account permissions.

Start with the current reference

Open API documentation in Create for the current endpoint definitions. The machine-readable schema is available at Create OpenAPI schema. Review the schema before implementing an integration; required inputs differ by operation.

Create an API key

Sign in, open API management, and create a key. Current keys have full access to the Create operations available to their account and projects; there is no permission selection. Store the key securely on your backend and send it using the documented bearer authentication. Never put a private key into a public webpage, browser bundle, screenshot, or Git repository.

Make your first request

Start with GET /api/v1/me to confirm your key's identity. Create an empty project with POST /api/v1/projects and JSON such as {"name":"Spring launch","aspectRatio":"9:16"}. The response includes the project and scene IDs. Creating this empty project does not submit generation work.

See Developers & API for copyable cURL and server-side JavaScript examples. Successful JSON responses contain data and meta.requestId. Inspect error.code and error.message on failures.

Handle asynchronous work

Discover models and account pricing with GET /api/v1/models. Submit generation using a project scene and a UUID Idempotency-Key, then poll the returned job. Download output only after completion. Retry the identical request with its original key; changed inputs require a new key. Do not automatically resubmit new paid work after an uncertain timeout.

Work with the editor

Start the editor session, sync media, and read the current timeline. Editing commands require the current revision and an idempotency key. On a revision conflict, read the latest timeline and review the intended edit. The editor catalog describes supported effects, transitions, captions, fonts, and properties.

The interactive editor requires a Central browser session with project edit access. A server API key does not sign a person into the browser editor.

Receive completion events

Register a public HTTPS endpoint using POST /api/v1/webhooks. Supported events cover production and review completion, failure, and cancellation, plus completed native renders. Generation jobs use polling; there is no documented generation-completed webhook.

Verify HMAC-SHA256 against the exact raw body and timestamp, reject timestamps outside five minutes, and deduplicate body.id. Delivery is at least once. Read the live schema for signature headers and retry behavior.

Maintain access

Respect account and project permissions. Current keys expire in 1–90 days and have a limit of 120 requests per minute per key. Respect Retry-After on 429 and 503 responses. Revoke unused keys and check the live reference when implementing your integration.