Shopify API version 2025-10 becomes inaccessible on October 16, 2026
Shopify retires API versions on a fixed quarterly schedule: each version lives a minimum of 12 months, then requests to it stop being served. Version 2025-07 already died in July 2026; 2025-10 is next.
Who gets hit
- 01
HTTP Request nodes/modules calling Shopify directly
URLs like
/admin/api/2025-10/orders.jsonor GraphQL endpoints with/api/2025-10/in the path. These fail outright once the version is locked. - 02
Custom apps and scripts built for a client and never touched since
The version was pinned at build time and forgotten — the most common case in agency handovers.
- 03
Platform-native Shopify nodes on old releases
Native n8n/Make/Zapier nodes generally track supported versions — but only if the node itself is up to date. Self-hosted n8n instances running old node versions inherit the old pin.
Typical client-visible symptoms after the deadline: order sync stops, fulfillment updates fail, inventory numbers freeze — with HTTP errors only visible in execution logs.
How to audit this week
- 01
Export client workflows (n8n JSON / Make blueprint) and search for
2025-07and2025-10in URLs. Anything found is either already broken or breaks on Oct 16. - 02
Move pinned calls to a current version (as of Aug 30, 2026 the newest stable is
2026-07, supported until July 2027) and read Shopify's release notes for fields deprecated between your old and new version. - 03
Re-run each touched workflow end-to-end against a dev store or a low-risk live flow before the deadline.
- 04
Mark the calendar:
2026-01dies January 16, 2027 — this repeats every quarter, forever.
This repeats quarterly — that's the point
Shopify sunsets a version every quarter. OpenAI retires 29 models one week after this deadline. Meta's Marketing API v24.0 dies ten days earlier. Watching all of it per client is exactly the job we do.