Back to monitors

shopify

Shopify API versions

Informational AI classification

ShopifyQL now versioned under GraphQL Admin API

Shopify updated the API versioning documentation to clarify that ShopifyQL is now versioned and follows the same quarterly release schedule as other GraphQL APIs. ShopifyQL queries made through the GraphQL Admin API use the selected API version, and unstable API calls resolve to the release candidate version. This is a documentation update reflecting the API's versioning model.

Alert history

  • Informational

    ShopifyQL now versioned under GraphQL Admin API

    Shopify updated the API versioning documentation to clarify that ShopifyQL is now versioned and follows the same quarterly release schedule as other GraphQL APIs. ShopifyQL queries made through the GraphQL Admin API use the selected API version, and unstable API calls resolve to the release candidate version. This is a documentation update reflecting the API's versioning model.

  • Informational

    Clean up UTM parameters in API documentation links

    Four section anchor links in the API versioning documentation had UTM tracking parameters (utm_campaign=social_care&utm_medium=community&utm_source=social) removed. This is a documentation cleanup that does not affect API behaviour or integrations — only the URL format of in-page links has changed.

  • Informational

    Add UTM parameters to API versioning documentation links

    Four anchor links in the API versioning documentation page have been updated to include UTM query parameters (utm_campaign=social_care&utm_medium=community&utm_source=social). This is a documentation-only change that tracks link source but does not alter any API behavior or specification.

  • Informational

    API versioning support timeline clarified with exact dates

    The Shopify API versioning documentation has been updated to use more precise terminology and dates. The term "unsupported version" has been changed to "inaccessible version", and the release schedule table now includes specific UTC timestamps (e.g., "July 16, 2026 15:00 UTC") instead of simple dates, plus three additional historical/current versions. These are clarifications to the documentation that do not alter the API's actual behavior or requirements.