Content, assets, and customer data

Learn where content overrides, translations, media assets, saved carts, wishlists, and account context belong.

Start here when your storefront experience depends on more than product records: localized words, channel-specific content, media assets, saved state, wishlists, or account context.

Use this page to choose the right surface before changing content, assets, saved shopper state, or account context. For endpoint paths, request fields, response fields, enum values, status codes, and validation behavior, open the relevant API reference.

The short model

Catalog data describes what can be sold. Content explains or adapts catalog data for a market, channel, campaign, or customer experience. Assets help people evaluate what they are seeing, with images, files, and videos each owning separate record and relationship APIs.

Customer data belongs to the signed-in or shared experience around the catalog: saved carts, wishlists, account identity, organisations, and attributes.

Choose the surface that matches the job:

Use Translations when localized text is attached to another record by parent reference.
Use Channel Content Overrides when presentation changes for one channel without changing the base product or variant record.
Use Images, Files, or Videos when the asset record, metadata, upload handoff, deletion, or item relationship changes.
Use Folders, Media, and Shareable Links when existing assets need public browsing, folder context, media search, or token-backed sharing.
Use DAM administration when trusted workflows change folders, placement, roles, operator search, or managed shareable links.
Use Cart or Wishlist when authenticated shopper state is being saved, listed, shared, or removed.
Use Auth, Users, Organisations, Organizations, Attributes, or Customer Groups when the job is identity, account context, profile data, organisation membership, structured account data, or account-specific pricing/access.

Choose the right surface

Job	Use	Why
Localize text attached to another record	Translations reference	Translation operations own localized content records and parent-reference reads.
Override channel-specific presentation	Channels reference	Channel content operations change channel-specific field values or relationships without changing the base record.
Upload or manage image records	Images reference	Images own image upload, metadata, deletion, and image relationships.
Upload or manage downloadable files	Files reference	Files own file upload, metadata, deletion, and file relationships. Auth API also exposes a smaller file surface for customer/account context.
Upload or manage video records	Videos reference	Videos own upload URL generation, metadata, deletion, bulk deletion, and video relationships.
Browse folders or media collections	Folders reference, Media reference, or Shareable Links reference	These routes read folder contents, public folders, media search results, folder-scoped media, or token-backed shareable-link resources.
Administer DAM folders, media placement, roles, operator search, or managed share links	DAM administration reference	These Management API operations change the DAM administration layer rather than the public asset-library read surface.
Save a cart reference	Cart reference	Cart routes save, list, and delete authenticated saved-cart references. They do not create orders.
Manage wishlists	Wishlist reference	Wishlist routes create, read, update, delete, add or remove items, and manage share tokens.
Read or change account context	Organizations and account access, Customer groups and pricing, and Attributes	Account context spans identity, organisations, account-scoped attributes, customer-group access, and customer-specific prices.

Contract facts to keep in mind

Use these facts to choose the right reference. Use operation pages for exact fields, auth, validation, status codes, and response shapes.

Browser-facing customer flows should use Auth API or public read surfaces. Trusted back-office workflows should use Management API operations for asset records, content overrides, translations, and channel presentation.
Use Folders, Media, and Shareable Links when existing assets need public browsing, folder context, media search, or token-backed sharing.
Use DAM administration when trusted workflows change folders, placement, roles, operator search, or managed shareable links. These Management API operations change the DAM administration layer rather than the public asset-library read surface.
Saved carts and wishlists are Auth API customer-state surfaces.
Creating a saved cart requires cart_id and source. Listing uses page and per-page, defaults to page 1 and 20 items per page, and rejects per-page above 100.
Saving the same cart reference for the same user returns a conflict.
Wishlist list can filter by a non-empty trimmed name query. When is_default is true, the write clears the previous default wishlist for the same user and app.
Add-item requests deduplicate repeated product IDs.
Wishlist share-token expires_at can be omitted or null for no expiration, but a supplied expiration must be in the future.

Events

Use Events after content or asset changes. The Event catalog covers translation, channel-content, AI-generated content, image, file, video, user-content, DAM folder, and DAM shareable-link events.

Use the Event catalog for exact event type strings, schema IDs, required fields, and payload fields. Use Events latest for delivery and retry behavior.

Where to go next

Need image delivery or DAM guidance? Start with Media and Asset library reads and DAM administration.
Need storefront implementation guidance that brings catalog, content, assets, and customer state together? Start with React SDK latest.
Need exact endpoint contracts? Use Reference, then choose the surface that owns the job.