Skip to main content
Brand kits store brand styling, content guidelines, parent brands, and approved image-source websites. API changes use the same saved kits and websites as the app. Use branding:read to list/get kits and branding:write to create, edit, or delete them. API keys and OAuth tokens resolve their organization automatically. Browser session requests must supply organizationId.

Create or edit

brandKit accepts every canonical kit field, including colors, typography, components, logo/icon URLs, personality, guidelines, aliases, and parent-kit IDs. Nested objects merge; arrays replace. Omitted fields are preserved on update and use defaults on create. parentBrandKitIds accepts at most one parent from the same organization. imageSourceUrls accepts HTTP(S) URLs or domain/path scopes such as manufacturer.example/products. Responses normalize them to host/path values. Use scopes that contain the relevant product pages; a specific landing-page path can exclude other product pages. An empty array clears the websites. Logo and icon images must use HTTP(S) URLs. Renaming a kit keeps its source websites attached. Deleting it removes its saved websites. Historical enrichment jobs retain their source snapshots until an explicit retry replaces them. List supports q, limit (1–1,000, default 20), and offset, returning items, total, and hasMore. Python provides the same operations through AsyncOmni as well.

Retry failed images with the updated kit

Use catalog:write for retry requests and catalog:read for progress. Pass a bulk import handle, a source import UUID, or review_<batch UUID> for a job opened in the Review page.
See bulk import retries for batch limits, completion semantics, and recovery.