Skip to main content

Changelog

Brand fonts — November 2026​

A brand can hold a heading and a body font file, and its ads are set in them. See Analyze a brand.

  • attachBrandFont, removeBrandFont and importGoogleBrandFont set, clear and import a brand's font file for the heading or body role, and need brands:write. A Google import is limited to 10 a minute and 100 a day; when Google Fonts cannot be reached it answers 503 brands.google_fonts_unavailable.
  • startMediaUpload takes licenceConfirmed, required for a font (a TTF or OTF file of up to 10 MB), which says its licence allows use in ads. Ask your customer before you set it. A font is kept for the brand and never listed in the media library.
  • getBrand and listBrands answer fontFiles with the files each role has; editing a brand or approving a new analysis leaves them as they are.
  • An ad's composition lists a stored font as fonts[].asset, a file of { key, mediaType } that ad-edit takes back with the rest of the composition, like its pictures. Where a font lacks a character the text needs, the text is set in a neutral font and the edit's warnings name it as font.

Runs on products — November 2026​

An Addon can run on an imported product without an uploaded photo, and a succeeded run's results belong to the product. See Run Addons on products.

  • An Addon input of type product takes { productId, variant?, image? }; left out, the photo input it fills gets the product's shop image. A shop image that is not loaded answers 409 orchestrator.product_image_not_ready.
  • getProduct names the run of each asset a run linked, and listProducts counts them in generatedImages.

Brands — November 2026​

API keys can analyze a shop's brand, approve it and manage the account's brands. See Analyze a brand.

Existing keys get brands:read and brands:write only when you add them.

Products — November 2026​

API keys can import a shop's products into catalogs. See Import products.

Redo — November 2026​

API keys can make finished results again with a note:

Batches — October 2026​

API keys can run an Addon on up to 50 items at once. See Run batches.

When the key that started a batch is revoked, expires or loses runs:create, the batch starts no more items. Existing keys get runs:manage only when you add it.

Run starts — October 2026​

API keys can start runs and list the account's runs:

Existing keys get runs:create only when you add it.

v1 preview — October 2026​

The first public API preview provides seven operations:

  • List the account's available Addons.
  • Start and complete a media upload.
  • List the media library and read an asset.
  • Read a known run's state or follow it as Server-Sent Events.

Calls use account API keys with explicit permissions. Run starts, the list of running runs, identity management and billing are outside this public API. Use the web app or a connected AI assistant to start runs.

This documentation update adds complete upload examples, run failure and stream handling, field descriptions, and guides for the refreshed web app. It does not add API operations or change their validation.

See Versioning and changes for the preview's compatibility policy and the API reference for the current contract.