URLs of custom apps calling deprecated APIs

Retired Boards Appdev Graphql Basics And Troubleshooting

Topic summary

A developer is troubleshooting persistent deprecated API call warnings in Shopify Admin despite updating their custom app and webhook configurations. The deprecated calls involve REST API endpoints for Order resources (customer fields, payment details, metafield types, and line item location fields) with migration deadlines in 2023-2024.

Core Issue:

  • The last_call_at timestamp continues updating even after code fixes are deployed
  • No method exists to identify the specific URLs/sources making deprecated calls
  • Developer suspects calls may originate from API testing tools (Postman/Insomnia) or unknown sources

Support Navigation Challenge:
Multiple users report difficulty accessing appropriate technical support:

  • Regular merchant support lacks technical expertise and redirects to forums
  • Partner Support requires a Partner Account (free to create)
  • Developers working as staff members (not partners) must create separate partner accounts
  • Email conflicts arise when staff emails are already registered
  • Collaborator account access recommended for shop-specific debugging with Partner Support

Status: Unresolved. Users are being directed to Partner Support for access to detailed log data that could identify deprecated call sources. The discussion highlights friction in Shopify’s support routing for in-house development teams.

Summarized with AI on November 17. AI used: claude-sonnet-4-5-20250929.
1

In Admin there are messages around a custom app calling deprecated endpoints (message below). I called the endpoint for the list of deprecated API calls (example response below) and remedied them in the application and deployed it. I have also updated the custom app configurations to use the latest webhook version, though the app doesn’t have any webhook subscriptions and I have validated there are no subscriptions through the REST endpoint. Despite doing this I am still seeing the last_call_at date change for most of the objects in deprecated_api_calls. Is there a way to see the URLs that are are calling the deprecated_api_calls so I can debug where these calls are coming from?

Message

Some of your custom apps and/or admin webhook subscriptions may not work as expected because they are using deprecated API versions. Contact your developer to ensure your store doesn’t experience disruptions. If you can’t contact the original developer, you can hire a Shopify expert.

This message is based on data from the last 14 days and may not reflect recently fixed apps and webhooks.

Response from API call to get a list of deprecated API calls

{
    "data_updated_at": "2023-05-22T13:59:59.000000Z",
    "deprecated_api_calls": [
        {
            "api_type": "REST",
            "description": "Some customer fields have been deprecated from the Admin REST API's Order resource.",
            "documentation_url": "https://shopify.dev/changelog/property-deprecations-in-the-rest-admin-api-order-resource",
            "endpoint": "Order",
            "last_call_at": "2023-05-22T09:27:44.000000Z",
            "migration_deadline": "2023-07-01T15:00:00.000000Z",
            "graphql_schema_name": null,
            "version": "2022-07"
        },
        {
            "api_type": "REST",
            "description": " The relationship between a ProductVariant and a FulfillmentService was changed in the 2022-07 API version.  A ProductVariant can be stocked by multiple fulfillment services. As a result, we recommend that you no longer use the following fields: - ProductVariant.fulfillment_service (GraphQL) (REST) - LineItem.fulfillment_service (GraphQL) (REST)  Instead, you should use inventory items and inventory levels if you need to find, or manage, where a product is stocked.  If you need to determine whether a product is a gift card, you should continue to use the ProductVariant.fulfillment_service field until an alternative is available.  Learn more about managing inventory quantities and states.  ",
            "documentation_url": "https://shopify.dev/changelog/property-deprecations-in-the-admin-api-order-and-lineitem-resource",
            "endpoint": "Order",
            "last_call_at": "2023-05-22T09:27:44.000000Z",
            "migration_deadline": "2023-07-01T15:00:00.000000Z",
            "graphql_schema_name": null,
            "version": "2022-07"
        },
        {
            "api_type": "REST",
            "description": "The `origin_location` and `destination_location` fields on line items have been deprecated from Admin REST API's Order resource.",
            "documentation_url": "https://shopify.dev/changelog/property-deprecations-in-the-admin-api-order-and-lineitem-resource",
            "endpoint": "Order",
            "last_call_at": "2023-05-22T09:27:44.000000Z",
            "migration_deadline": "2023-07-01T15:00:00.000000Z",
            "graphql_schema_name": null,
            "version": "2022-10"
        },
        {
            "api_type": "REST",
            "description": "The gateway, payment_details, and processing_method fields on the Order resource have been removed.\n\n\nThe `orders/transactions.json` REST endpoint, and the `transactions` GraphQL connection provide correct information per transaction set.\n",
            "documentation_url": "https://shopify.dev/changelog/payment-properties-deprecation-on-the-admin-api-order-resource",
            "endpoint": "Order",
            "last_call_at": "2023-05-22T09:27:44.000000Z",
            "migration_deadline": "2024-01-01T15:00:00.000000Z",
            "graphql_schema_name": null,
            "version": "2023-04"
        },
        {
            "api_type": "REST",
            "description": "`Metafield.valueType` has been removed. See `Metafield.type` for type information.",
            "documentation_url": "https://shopify.dev/changelog/online-store-2-0-new-metafields-type-system-and-dynamic-sources",
            "endpoint": "Metafield",
            "last_call_at": "2023-05-22T09:26:40.000000Z",
            "migration_deadline": "2023-01-01T15:00:00.000000Z",
            "graphql_schema_name": null,
            "version": "2022-04"
        },
        {
            "api_type": "REST",
            "description": "The Fulfillment API has been deprecated and replaced with Fulfillment Orders.",
            "documentation_url": "https://shopify.dev/api/release-notes/2022-07",
            "endpoint": "Fulfillment",
            "last_call_at": "2023-05-22T09:50:47.000000Z",
            "migration_deadline": "2023-07-01T15:00:00.000000Z",
            "graphql_schema_name": null,
            "version": "2022-07"
        },
        {
            "api_type": "REST",
            "description": "The `total_price_usd` field on `Order` has been deprecated from the Admin REST API's Order resource.",
            "documentation_url": "https://shopify.dev/changelog/property-deprecations-in-the-admin-api-order-and-lineitem-resource",
            "endpoint": "Order",
            "last_call_at": "2023-05-22T09:27:44.000000Z",
            "migration_deadline": "2023-07-01T15:00:00.000000Z",
            "graphql_schema_name": null,
            "version": "2022-10"
        }
    ]
}
2

I have this same issue, @0developer .

Did you find out anything yet? Thank you kindly.

3

Hi @0developer , If you are using any Clients e.g. Postman or Insomnia to make calls on the same API key this can often explain the outliers in the API health reports. In some cases if there are not too many source URLs we can help developers to locate them using log data. If you want to reach out directly to our partner support team they can try to assist further. Hope that helps!

4

@ShopifyDevSup Hello, thank you for the reply!

“If you want to reach out directly to our partner support team they can try to assist further.”

I’d love to get some help with this as I have no idea why Shopify is giving me this warning as it seems to me I have resolved all the issues. How can I contact them?

5

If you login to the partners dashboard there are directions there. https://help.shopify.com/en/support/partners/login

6

Do you mean the regular support? In there I will get no help since they don’t know any tech. In fact, they were the ones who referred me to this forum.

Being referred around in an endless loop is not a good support experience, just got to say that.

My client is a global sports brand and a Shopify Plus customer and if someone with some actual tech experience could help me out I would really appreciate it.

(Sorry I thought this was my own post: https://community.shopify.com/c/customers-discounts-and-orders/need-help-with-our-own-custom-app-order-resource-deprecations/td-p/2172414)

7

Hey @Dawid_Umain ,

When we refer to ‘Partner Support’ this is different than our regular ‘Merchant Support’.

Partner Support can be directly accessed when logged into your Partner Dashboard under ‘support’ where you would pick your topic and then be presented with contact options.

We ask that you do this as your question requires us to have an authenticated look at the store you are working on and this can not be accomplished in a public forum. I can also assure you that our Partner Support members are well versed in deprecation topics and shouldn’t be redirected you to the forums, you can reference this post as well if you need to.

I hope that helps!

KN

8

Hello, @ShopifyDevSup , thank you so much for replying!

The thing is, I don’t have a partner account. The company I am a develper for is a Shopify Plus customer and they simply added me as Staff will full access, not a partner. In this scenario, how would you suggest I get in contact with someone who understands tech?

Thank you!

9

Hey @Dawid_Umain :waving_hand:

You can sign up for a partner account for free here. I don’t believe we limit folks in terms of who can sign up for a partner account. Anyone can sign up!

In the past, I’ve seen some merchants with in-house or external developer teams make use of partner accounts specifically for custom apps on their shops, so this might be a good way to get in touch with our Partner Support team as mentioned above. You should be able to set up an account right away and get in in touch with our Partner Support team as soon as the account is set up.

One recommendation that might make it easier as well is if you request collaborator access on the shop after you’ve set up your Partner Account (more info on that here). You did mention that you already have a staff account on the shop - but if you had a collaborator account specifically, my understanding is that it would allow our Partner Support team to more quickly/effectively help out with shop specific questions.

Generally, depending on the level of permissions your client gives you on their shop through the collaborator account, our Partner Support team can assist with technical questions through some of our internal technical support or product development teams.

Hope this helps - thanks for your patience on this too. I definitely understand where you’re coming from here, it’s not an ideal experience to be redirected multiple times. When it comes to shop specific log data, we try to be as secure as possible, so we can’t always help through public-facing channels like the forums. Setting up a partner account and then a collaborator account on the shop would be the quickest support route when it comes to getting help with technical questions that are shop-specific or deal with sensitive data (including logs related to deprecated calls on specific shops).

If you do get in touch with Partner Support, I would share this thread with them and let them know you were speaking with the Developer/API Support team on the forums - this might help provide some context for our Partner Support folks as well and expedite support.

Al | Shopify Developer Support

10

Excellent, I will try that! Thank you for the help, @ShopifyDevSup !

11

@ShopifyDevSup I can’t do it with my work email, as that is already the email I have as Staff in the store. Do you recommend I use my private email for that, or create a new one, or what…

This is not a good experience at all, just to get some tech help.

"To add this store, the following errors need attention:

An account’s email on the store is the same as your partner business email. You can log into the store using that user, or ask the owner of the shop to remove the user."

I will try to contact the support anyway, let’s hope that works.