Deprecated_api_calls.json returns "Not found" with new Dev Dashboard token (works with legacy app token)

Dev Platform
1

Hi everyone,

I’m trying to check deprecated API calls for my store, but I’m getting a “Not found” error with tokens generated from the new Dev Dashboard. The same endpoint works perfectly with tokens from legacy apps created in Store Admin > Settings > Apps and sales channels.

How I generated the token (OAuth flow via Dev Dashboard app):

Step 1 - Authorization Request: I redirected to Shopify’s authorization endpoint:

GET https://{shop}.myshopify.com/admin/oauth/authorize
  ?client_id=MY_API_KEY
  &redirect_uri=https://myapp.com/callback
  &state=random_nonce_123
  &scope=read_products,write_products,read_orders

User approved the permissions.

Step 2 - Token Exchange: After receiving the authorization code in the callback, I exchanged it for the access token:

POST https://{shop}.myshopify.com/admin/oauth/access_token

Body:
{
  "client_id": "MY_API_KEY",
  "client_secret": "MY_API_SECRET", 
  "code": "AUTHORIZATION_CODE_FROM_CALLBACK"
}

Response received:

{
  "access_token": "shpat_xxxxxxxxxxxxx",
  "scope": "read_products,write_products,read_orders"
}

The token works - I can successfully call other endpoints like /admin/api/{version}/products.json and /admin/api/{version}/orders.json.

The problem:

When I call the deprecated API calls endpoint:

curl -X GET "https://my-store.myshopify.com/admin/api/{version}/deprecated_api_calls.json" \
  -H "X-Shopify-Access-Token: shpat_xxxxxxxxxxxxx"

I receive:

{
  "errors": "Not found"
}

However, if I use an access token from a legacy custom app (created in Store Admin > Settings > Apps and sales channels > Develop apps), the same endpoint works correctly and returns the deprecated API calls data.

Since legacy custom apps can no longer be created after January 1, 2026, this is becoming a problem for monitoring API deprecations going forward.

Questions:

  1. Is deprecated_api_calls.json not supported for apps created via the Dev Dashboard?

  2. Are there additional scopes or permissions required for Dev Dashboard apps to access this endpoint?

  3. Is there an alternative way to check deprecated API usage with the new authentication flow?

Thanks for any help!

2

Hi @Sebastiano_Piccione First, glad you were able to get your app up and running.

That’s correct that deprecated_api_calls.json is not available for any app created from the dev dashboard. We will update our documentation to make this clear.

Within the dev dashboard every app gets clear notification when they are using an API that is going to be undergoing breaking changes (see below for a screenshot). You will see a banner like this on the app. And that will take you to the API Health report that will provide detail about exactly what calls you are making that are going be breaking changes.

In addition you will receive Emails as well if your app is making breaking API changes close to the date when the old API calls will stop being supported.

Does this give you what you need?

Screenshot 2026-01-29 at 7.58.00 AM
Screenshot 2026-01-29 at 7.58.00 AM2758×974 258 KB

3

Hi eytan-shopify,

Thanks for the clarification.

I want to stress that this is a serious limitation for Shopify Partners operating at scale.

We are a Shopify Partner agency managing ~200 custom apps across multiple merchants. Relying on manual checks in the Dev Dashboard UI, banners, or email notifications is not operationally viable for us. We need a programmatic, automated, machine-readable way to monitor deprecated and breaking API usage across apps and stores.

The deprecated_api_calls.json endpoint fulfilled exactly this role for legacy custom apps. Removing access to it for Dev Dashboard apps without providing a functional API replacement creates a regression in observability and compliance tooling.

To be explicit:

  • Dashboard-only visibility does not scale.

  • Email notifications are insufficient for automated monitoring and CI/CD workflows.

  • We need an API or webhook-based alternative that can be queried centrally.

Can you confirm:

  1. Whether a replacement API (or GraphQL equivalent) for deprecated API usage is planned?

  2. If there is any supported way today to retrieve API Health / breaking change data programmatically for Dev Dashboard apps?

  3. If not, what is the recommended strategy for partners managing hundreds of apps who must ensure forward compatibility?

Without an automated solution, this significantly impacts our ability to proactively manage API deprecations.

Thanks in advance for clarifying.

4

Any update?
Thank you