Activity & operational state

Read who changed what, when: the account-wide feed (filterable by entity type, action, store, actor, source, and the saved-vs-published lens) or, with master_id, one entity's timeline including its variants. Each event carries the field-level before/after changes and, for publish events, the outcome detail. Newest first.

Read the home summary: item and store-version totals, pending updates, items published today, the six most recently updated items with their status, at-a-glance counts (collections, files, metaobjects, variants), and per-store publish coverage (published / pending / failed / total).

Evaluate the catalog on demand without writing anything: analysis "completeness" lists the items missing values for the given fields (per store, or every store), analysis "value_divergence" lists the items whose stores disagree on the given fields (always cross-store) with each store's value and a signature per field. Both page through matches and report exact totals. Fields: the type's scannable fields plus any mf: key; completeness also takes "Image" and "Collections" for products, divergence "Media", "Media Alt Text", "Variant count" (products) and "Members" (collections). At most 40 fields.

• Extended timeout. 120 s per call — the operation runs server-side orchestration or a live Shopify read.

Read whether a whole-shop refresh from Shopify is running on one store, its live stage and progress counters when it is, and the last run's result: what was refreshed, created, unchanged or failed per entity class, the deletion candidates it found (refresh deletes nothing itself — they await review), and its warnings.

Read whether a store import or whole-shop refresh is awaiting review (while one is unfinalized, every write in the PIM answers 423 pim_locked): the run (store, mode, status, timestamps), per-type tallies (matched, created, reviewed, refreshed, deleted), and — with include_deletions on a refresh run — the full deletion-candidate list with each candidate's keep decision. status "none" means nothing is under review.

List the items of the open import or refresh review for one entity type: each with its outcome (matched, created; refreshed or deleted on a refresh run), match score and the keys that matched, whether it was reviewed, its parent, nested variants for products, and on a refresh run the fields the refresh changed. Answers 409 when nothing is under review.

For the open refresh review, read the field-level before/after changes the refresh applied to one item: the shared (all-store) fields and the store's own fields. Refresh runs only; answers 409 for an import review or when nothing is under review.

For the open import/refresh review, preview which existing items one imported item would match under the run's matching rules (or a proposed match_config): each candidate's score, the keys that fired, and whether it would match. Read-only.

Read the account's current supplier-file import run: its status, source file, mode, row count, the saved column-to-field mappings, the match selection (which stores, which key), manual matches, and — once committed — how many entities were written or failed. status "none" means no run is in progress.

No arguments.

Page through the computed plan of the current supplier-file import: totals (matched, unmatched, ambiguous, to create, changed and invalid fields) and each row's outcome, the item it matched (or would create), and its field-level before/after changes with validation flags. Answers 409 until the plan has been computed in the wizard.

List the account's saved bulk-edit grid layouts for one entity type, each with its name and its config — the grid's own layout object (columns, filters, sort, grouping) exactly as the interface saved it. Apply one by feeding its filter/sort into list_bulk_edit_rows_v1. entity_type values: product, collection, variant, media, blog, article, or metaobject_entry:<definition id>.

List the account's saved mapping templates of one kind: "import" templates snapshot a supplier-import wizard configuration, "export" templates an export field selection. Each carries its name and config exactly as the interface saved it; an export template's field selection can be fed into export_bulk_edit_v1.