> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/core/shopify/api-versions.md).

# API versions

The Shopify API supports **versioning** for their REST and GraphQL admin APIs. (Learn more: [shopify.dev/api/usage/versioning](https://shopify.dev/api/usage/versioning).)

Each Mechanic task has an individually-configured Shopify API version, defaulting to the latest stable version at the time of the task's creation. A task's version will apply to all Shopify API calls generated by its task code, in addition to all calls performed by that task's actions.

Each stable Shopify version is supported for one year. 30 days before a version ends support, tasks on that version will be silently upgraded to the next stable version. As a consequence, versions that are unsupported (or are within 30 days of no longer being supported) are not available in Mechanic.

## Task usage

{% content-ref url="/pages/-MXYcOufZYeFrCK1-jtF" %}
[Shopify API version](/core/tasks/shopify-api-version.md)
{% endcontent-ref %}

## Deprecations

Every quarter, Shopify releases a new version of the Admin API, and simultaneously removes the oldest version of the admin API. (Subsequent calls to removed APIs will be responded to by the oldest still-supported version.)

As Shopify prepares to pull support for specific API calls, deprecations are announced, and are communicated in API responses.

[Learn more about Shopify's deprecation practices](https://shopify.dev/concepts/about-apis/versioning#deprecation-practices)

{% hint style="info" %}
Deprecations are ignored for the latest stable version of the Shopify API, i.e. the version most recently released. Tasks whose runtime settings are configured for the latest stable version will not be flagged for deprecations, even if they use deprecated Shopify API features.
{% endhint %}

### Identifying deprecations

If support for a task's Shopify API version will be pulled soon, its deprecations will be shown above the main task list in Mechanic.

<figure><img src="/files/B8RGpjOuT1nWWQz4JHD1" alt=""><figcaption></figcaption></figure>

Deprecation details are available in the advanced task editor, in the Runtime tab.

<figure><img src="/files/7mDjropYMXMbZZuvPyBL" alt=""><figcaption></figcaption></figure>

For local task development, use the [Mechanic CLI](/resources/mechanic-cli.md) to list unresolved deprecations for the shop:

```bash
mechanic shop deprecations
```

Trusted scripts and monitoring tools can use [`GET /v1/shop/deprecations`](/resources/mechanic-cli/mechanic-task-sync-api.md) with a Mechanic API token.

### Resolving deprecation warnings

Deprecation warnings can be dismissed by doing one of the following:

* Selecting a new Shopify API version for the task
* Updating the task code
* Disabling the task
* Deleting the task


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.mechanic.dev/core/shopify/api-versions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.