HARD DEADLINE · OCT 16, 2026 · 15:00 UTC
…

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 becomes inaccessible. A call to an inaccessible version doesn't fail: Shopify falls forward and answers with the oldest version still accessible. So after Oct 16 a 2025-10 call gets a 2026-01 answer, and what breaks is any field your workflow reads that was removed or renamed in between.

Who gets hit

  1. 01

    HTTP Request nodes/modules calling Shopify directly

    URLs like /admin/api/2025-10/orders.json or GraphQL endpoints with /api/2025-10/ in the path. The URL keeps working once the version is locked; the response comes from a newer version, and steps that read a changed field get the wrong data or an error.

  2. 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.

  3. 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.

Because the call still goes through, the damage is quieter than an outage: a GraphQL query that asks for a removed field errors, while a REST step that reads a removed field just gets nothing back and the run can still show as successful.

How to audit this week

  1. 01

    Export client workflows (n8n JSON / Make blueprint) and search for /admin/api/20 in URLs. Anything pinned to 2025-10 or older is, or from Oct 16 will be, answered by 2026-01 instead of the version it was built against.

  2. 02

    Read Shopify's release notes between the pinned version and 2026-01 for the fields each step actually uses, then move the call to a current version (as of Oct 9, 2026 the newest stable is 2026-10, accessible until October 16, 2027). Bumping the number without checking the fields only moves the problem.

  3. 03

    Re-run each touched workflow end-to-end against a dev store or a low-risk live flow before the deadline.

  4. 04

    Mark the calendar: 2026-01 dies January 16, 2027 — this repeats every quarter, forever.


Source: Shopify official API versioning policy — shopify.dev/docs/api/usage/versioning. Dates verified Aug 30, 2026. Fall-forward behaviour verified Oct 9, 2026: “If your app targets an inaccessible version, Shopify falls forward and responds using the oldest accessible stable version.”

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.

See pricing Free dependency report