Mango9 Create documentation

Brand libraries and templates

Reuse brand media and automate repeatable edits through the API.

Keep a reusable brand library

Account owners can create named brand libraries with POST /api/v1/brands. Upload permanent brand media using POST /api/v1/assets with brandId, then list the library's assets when preparing a campaign.

Bring brand material into a project

Attach selected owned asset IDs with POST /api/v1/projects/{id}/assets. Start the editor session and sync media before referencing those assets in an edit. The original brand asset stays in the library.

Define a versioned template

Publish a template with a client UUID, version 1, named typed slots, and editor commands. Whole-value slot placeholders are substituted when a variant runs. Slot choices can constrain text, color, or font inputs. Publish the next sequential version when the template changes rather than rewriting an earlier version.

Prepare a batch of variants

  1. Prepare separate projects and start their editor sessions.
  2. Attach and sync the required media.
  3. Read each project's current timeline revision.
  4. Submit 1–20 variants with their required slot values.
  5. Use a dry run to validate edits before applying them.
  6. Track each separate production job and review the rendered result.

Include the documented profile command in a template when producing aspect variants. A template request does not automatically create the required editor projects.

Example workflow

An internal campaign tool can keep approved product imagery in a brand library, prepare a project for each message, and substitute approved copy into a common edit. Your team still reviews the result before delivery.

See Developers & API and the live reference for current schemas and account requirements.