Entity creation

Create one item as a DRAFT the way the interface does: the shared item with its attributes, then one per-store version per store in channel_ids carrying that store's attributes (channel_attributes[store id], e.g. Title, Status, Handle). A Product also gets its default variant; add option dimensions with create_product_option_v1 and further variants with type "Variant" + parent_master_id (a variant's option values are attributes named "Option: <option name>" on its per-store attributes; variants are fanned out to the parent's stores server-side). An Article needs parent_master_id = its blog. Blog, Article, and Page need the account's online-store content capability to be listed and published. A store whose version could not be created is reported in failed_channel_ids — the item still exists. Publish afterwards with publish_master_v1.

• Extended timeout. 120 s per call — the operation runs server-side orchestration or a live Shopify read.
• Drafts only. Changes land in Peak PIM; nothing reaches Shopify until a publish.

Declare one option dimension (Size, Color, …) on a product, per store — the initial option configuration variants need. Each store gets the option's name and values (up to three dimensions per store); existing variants on that store receive the first value, and the optional variants directives rename existing variants or mint new ones per value. Already-published stores are republished for the new dimension, which is why this tool reaches Shopify; a store that refuses it stays pending.

• Extended timeout. 120 s per call — the operation runs server-side orchestration or a live Shopify read.
• Reaches your stores. Annotated open-world and destructive; the in-app assistant always asks for confirmation before running it.

Create the per-store version of an existing item on one store it is not on yet — a product (its variants follow), collection, file, definition, market, catalog, blog, article, page, or metaobject entry — as a DRAFT. source_projection_id copies another store's version as the starting point (attributes adapted to the target store, references remapped, and for a collection its source definition). A variant needs its product on that store first. Publish afterwards with publish_master_v1.

• Drafts only. Changes land in Peak PIM; nothing reaches Shopify until a publish.

Define a new metafield (namespace.key, name, Shopify type, owner type, validations, taxonomy category constraints, capability options) as a DRAFT on the selected stores. Owner types: Product, Variant, Collection, and — with the online-store content capability — Blog, Article. A definition with the same namespace.key for that owner answers 409. Publish it with publish_master_v1 before writing values to it.

• Drafts only. Changes land in Peak PIM; nothing reaches Shopify until a publish.

Define a new structured-content type (a type key without spaces, a name, at least one field definition with key/name/type) as a DRAFT on the selected stores — or PIM-only when channel_ids is empty. A same-type definition answers 409. Publish it with publish_master_v1; then add records with create_metaobject_entry_v1.

• Drafts only. Changes land in Peak PIM; nothing reaches Shopify until a publish.

Create a record under a metaobject definition as a DRAFT on the given stores (each store must already carry the definition), with a name and an optional handle (derived from the name otherwise; a handle already used under the definition answers 409). Fill its fields afterwards with update_projection_attributes_v1 (keys mo:<field key>) and publish with publish_master_v1.

• Drafts only. Changes land in Peak PIM; nothing reaches Shopify until a publish.

Define a new PIM-only custom field: a name, a slug (letters, digits, underscores — immutable afterwards), the entity kind it applies to (Product, Variant, Collection, Media; Blog and Article with the online-store content capability), a supported type, options for select types, a formula for the formula type, and an optional mf: target key. Values are then written per store under custom:<slug>. Never published to Shopify.

• Drafts only. Changes land in Peak PIM; nothing reaches Shopify until a publish.

Create a Shopify market (name, region country codes, optional currency) as a DRAFT on the selected stores (default: every store). Publish it with publish_master_v1; then add catalogs with create_catalog_v1.

• Drafts only. Changes land in Peak PIM; nothing reaches Shopify until a publish.

Create a catalog (price list + publication) attached to a market as a DRAFT on the selected stores (default: every store the market is on): a title, a required currency, an optional percentage price adjustment, and whether it auto-publishes. The catalog's market is queued for publish; pending_publish_failed in the result means the catalog exists but the market must be published by hand — do not retry the create.

• Drafts only. Changes land in Peak PIM; nothing reaches Shopify until a publish.

Duplicate a product, collection, or metaobject entry into the selected stores with the interface's own options: a new title and handle, a product's status (default draft), whether to carry media, SKUs, barcodes, translations (default off), a collection's sources, a product's hand-picked collection memberships, and the sales-channel selection. NOTE: like the interface, the copy is PUBLISHED to the target stores as part of the duplicate — this reaches Shopify. Mint a progress_token (8–64 letters, digits, dashes) and poll get_duplicate_progress_v1 with it while the call runs. The result reports the new item, publish outcome, and what could not be carried.

• Extended timeout. 120 s per call — the operation runs server-side orchestration or a live Shopify read.
• Reaches your stores. Annotated open-world and destructive; the in-app assistant always asks for confirmation before running it.

Read the live step progress of an in-flight duplicate by the progress_token given to duplicate_master_v1: each step (entity, variants, images, sources, translations, publish, collections) with its status, and whether the run finished. Answers 404 until the run has started writing progress, and again once the record expires (10 minutes).