Your catalog, programmable.

Peak PIM keeps one canonical version of every product, variant, collection, and media file across all your Shopify stores. These pages document the two ways to build on it: a versioned REST API for your systems, and a remote MCP connector for your AI assistants.

API quickstart Connect an AI assistant

Start here

Core concepts

Canonical values, store versions, attributes, publish state — the one mental model behind every endpoint and tool.

Start here

API or MCP?

Two surfaces, one catalog. When to reach for scoped API keys, and when to hand an assistant a consented connection.

REST API · v1

Peak PIM Public API

Cursor-paginated reads across the whole catalog and operations layer, plus the first write endpoints for data health — behind scoped API keys.

MCP · remote connector

Peak PIM MCP connector

28 tools that let Claude, ChatGPT, or any MCP client browse, compare stores, draft edits, and publish — behind an OAuth consent you control.

What you can build

Syncs and exports — walk the whole catalog with cursor pagination, then poll updated_since to stay current in your ERP, data warehouse, or storefront. Guide →
Multi-store audits — compare an item's canonical values against each store's version to find drift in titles, prices, or SEO fields. Guide →
AI catalog operators — let an assistant find every variant missing a SKU, draft the fixes, and publish them to the stores you choose. Guide →
Publish monitors — track pending_publish and last_publish_status to alert on failed or forgotten publishes. Guide →
Data-health automation — scan the catalog, page through issues, and run remediation batches that fill gaps and reconcile divergent values as drafts. Guide →

How the two surfaces relate

Both speak the same catalog. The REST API is the versioned, supported contract for code — keys, scopes, and stability guarantees. The MCP connector wraps the same data as tools an AI assistant can call, authorized per-connection through an OAuth consent screen with three permission tiers (read / read & write / read, write & publish).

One model to know

Every entity in Peak PIM exists twice: the canonical values every store inherits, and one store version per connected store that can override them. The REST API calls these the entity and its store versions; MCP tool names use the internal words — master for the canonical item, projection for a store version. Same concept everywhere. Core concepts walks through the whole model.

For LLMs and agents

This site is written to be machine-readable too. Point your model at /llms.txt for an index, /llms-full.txt for the entire documentation in one plain-text file, or /api/openapi.yaml for the formal API contract.