Shopify Catalog REST API shuts down on 2 November

Apps still using Shopify’s Global Catalog REST API must migrate before 2 November 2026. Shopify’s 9 October notice says the service will stop accepting traffic, including requests against saved catalogs. The REST API was deprecated in April.

The replacement is Global Catalog MCP, using the Universal Commerce Protocol (UCP). This deadline concerns integrations that call the retiring API. Store owners should ask the developer of an affected product-discovery app about migration; there is no general instruction here to rebuild a Shopify storefront.

Map the calls, then test their responses

Shopify gives three replacements:

• REST search calls move to search_catalog.
• Product and variant lookups move to get_product.
• Bulk lookup calls move to lookup_catalog.

Send requests to https://catalog.shopify.com/api/ucp/mcp. Include your agent profile URL in meta.ucp-agent.profile on every request. Saved catalogs use catalog.catalog_id rather than a dedicated endpoint URL. Authentication remains based on bearer tokens generated from Dev Dashboard credentials.

A URL swap is only part of the work

The Global Catalog documentation describes product discovery across multiple merchants. Search and lookup find products; get_product helps resolve variants, prices and seller checkout links. Single-store discovery has separate Storefront Catalog documentation.

The tools use UCP request and response schemas. An agent’s advertised capabilities affect what becomes available: Shopify documents base catalog capabilities plus Shopify extensions for enriched fields. Review the profile as well as the request code.

Some returned descriptions, attributes and specifications are marked as inferred. Shopify warns that these fields can vary in accuracy or be absent. Do not treat every enriched response field as text supplied by the merchant.

A practical migration check

Our recommendation is to search your integration code and configuration for discover.shopifyapps.com, then list which live features depend on those calls. Include saved catalog jobs and background tasks, not only the main search screen.

Test representative searches, a known product, a variant and a saved catalog against the new service. Check the resulting product links and the way your interface handles missing fields. Record failures before switching production traffic, and monitor the replacement after release.

For merchants, a useful vendor question is: “Does this app still call the Global Catalog REST API, and when will you verify its replacement?” Ask for confirmation against the feature you use.

Our Catalog product-media guide covers the separate opportunity to surface videos and 3D models. Those optional media capabilities do not remove this REST retirement deadline.