Shopify API versioning

API versioning allows Shopify to continuously evolve the platform while offering third-party developers a predictable path for feature upgrades and deprecations.

To ensure you always know about upcoming API changes, follow the Changelog and always keep your contact information up to date in the Partner Dashboar .

Versioned vs. unversioned APIs

Versioned APIs Unversioned APIs
  • Admin API (GraphQL and REST)
  • Storefront API
  • Webhooks
  • Developer previews
  • OAuth endpoints (including AccessScope)
  • Liquid
  • Shopify Scripts
  • Ajax API
  • Analytics API
  • Any other resources not explicitly listed as versioned
  • Release schedule

    Shopify releases a new API version every 3 months at the beginning of the quarter. Version names are date-based to be meaningful and semantically unambiguous (for example, 2020-01). Below is an example release schedule for 2020:

    Stable version Release date Date stable version is supported until
    2021-01 January 1, 2021 January 1, 2022
    2021-04 April 1, 2021 April 1, 2022
    2021-07 July 1, 2021 July 1, 2022
    2021-10 October 1, 2021 October 1, 2022

    Stable versions are released at 5pm UTC.

    Each stable version is supported for a minimum of 12 months. This means that there are at least 9 months of overlap between two consecutive stable versions. When a new stable version is introduced and contains changes that affect your app, you have 9 months to test and migrate your app to the new version before support for the previous version is removed.

    We strongly recommend updating your apps to call the latest stable API version every quarter. However, if your app calls a stable version that is no longer supported, then Shopify falls forward and responds to your request with the same behaviour as the oldest supported stable version. For example, when Shopify removes 2019-07, API requests that call version 2019-07 will be served version 2019-10, because that will be the oldest supported stable version.

    If your request doesn't include a version, then the API also defaults to the oldest supported stable version. However, we do not recommend relying on this behaviour for adopting deprecated changes. As you update your app, you should specify the API version with every request. By making your app version aware, you anchor your code to a specific set of features that are guaranteed to behave in the same way for the supported timeframe.

    Example version support schedule

    Calling an API version

    Shopify API versions are explicitly declared in the URL that your app calls:

    • REST Admin API URLs: /admin/api/{ version }/{ endpoint }.json
    • GraphQL Admin API URL: /admin/api/{ version }/graphql.json
    • Storefront API URL: /api/{ version }/graphql.json

    For example, the following URLs call version 2021-07:

    • Rest Admin API URL: /admin/api/2021-07/products.json
    • GraphQL Admin API URL: /admin/api/2021-07/graphql.json
    • Storefront API URL: /api/2021-07/graphql.json

    There are several supported versions of the APIs available, and you specify the version that you want to use by substituting the version name in the URL. There are three types of API versions: stable, release candidate, and unstable.

    Shopify's API responses contain the header X-Shopify-API-Version, which returns the API version that was used to execute the request. When you keep your app updated, this matches the API version that's specified in your request. If the returned version is different, then your app is out of date and is using the default API version.

    Release candidates

    Release candidates let you see what changes are scheduled for release in the next stable version so that you can begin updating your app as early as possible. API release candidates are made available on the same date that we release our stable versions. For example, when version 2020-01 is released on January 1, 2020, the release candidate for version 2020-04 will also become available.

    Both backwards-incompatible and backwards-compatible changes can be added to the release candidate so that they’re available to you ahead of the stable release. For this reason, we recommend that you don’t use release candidates in production.

    Unstable API versions

    There is always an unstable version of the APIs available. The unstable versions contain features and changes that are still in progress, and we make backwards-incompatible and backwards-compatible changes to them regularly. Generally, changes appear in the unstable version before a stable release, but there is no guarantee that changes in the unstable version will eventually be released. A feature might be added to an unstable version but then be removed later.

    You can use the unstable API versions to test new changes and features early, but you should not use them in production.

    • Example REST Admin API call: https://{shop}
    • Example GraphQL Admin API call: https://{shop}
    • Example Storefront API call: https://{shop}

    Deprecation practices

    Part of a Shopify API can be deprecated if it becomes unnecessary, unsafe, or outdated. It's marked as deprecated when it's removed in a newer version of the API. The deprecation is then retroactively applied to previous stable versions of the API. When a deprecation is introduced, any further details and any relevant migration information is announced in the developer changelog.

    Because each version is supported for a minimum of a year, there are always at least 9 months of overlap between versions for you to update your app to support deprecations.

    Apps using deprecated resources

    Screenshot of merchant warnings for unsupported apps

    If a public app or sales channel continues to use unsupported resources after the upgrade deadline, it will be delisted from the Shopify App Store. Also, merchants who inst