Create documentation / Developers

Brand libraries and templates

Reuse brand assets in the app and build repeatable, versioned edits through the API.

In this guide
Reusable brand material and a template workflow for creating reviewed variants.

1. Organize reusable brand media

Open Brands from Create's main menu to work with brand material. When creating a project, choose its Brand to set the right context.

For an integration, use POST /brands to create a named library. Upload brand media with POST /assets and its brandId, then list the assets when preparing a project.

Keep logos and approved imagery clearly named so your team can reuse the correct files.

Search /brands in the endpoint reference to find the brand library operations and their request details.

2. Attach brand assets to the working project

Send owned asset IDs to POST /projects/{id}/assets. Start the project's editor session and sync media before referencing those assets in commands.

The brand library keeps the reusable original; the project determines how it appears in an edit. Check that every required asset is available before applying a template.

3. Publish a versioned template through the API

Templates in this guide are API resources. Open API documentation → Endpoint reference, search /templates, and inspect the create-template schema.

Define a client UUID, version 1, named typed slots, and the editor commands that form the template. Slots represent values that change between variants, such as text, color, or font. Use whole-value slot placeholders as documented in the schema.

Publish the next sequential version when the design changes. Keep earlier versions available to integrations that still use them.

Expand the template operation to inspect its version, slots, editor commands, and request schema.

4. Validate and generate variants

  1. Prepare a separate project for each variant.
  2. Start its editor session, attach the required media, and sync the files.
  3. Read each project's current timeline revision.
  4. Prepare slot values and submit 1–20 variants using the documented request shape.
  5. Use a dry run to validate edits before applying them.
  6. Track the separate production jobs and review each render.

For aspect-ratio variants, include the appropriate profile command. Create the required projects before submitting the template request.

5. Review each output before delivery

Check the logo, copy, font, crop, and duration of every variant. Preview how different text lengths and images fit the frame.

Download the output after completion. Keep the project and template version with the delivered file so your team can reproduce or revise it. See API and integrations for authentication, job handling, and retries.