Hey guys, I’m using the graphql apis exclusively when fetching products, however I’m still getting the Rest Api warning messages because I’m still using the Products Count rest api from time to time for unsupported queries on GraphQl… Anyways you guys can untangle the products/count.json endpoint from this? How is it related to supporting 2048 variants anyways? This would be very helpful.
1 Like
Hi @jason_engage,
Regarding the products/count.json endpoint, I can confirm that this endpoint is and has been detected as one of the deprecated REST /products or /variants endpoints with the changes made with the new Product Model API.
I do understand that the documentation doesn’t specifically mention the /products/count endpoint, and I will be following up with our developers internally to confirm the behaviour here, and will follow up in this thread once I get confirmation on the actual expected behaviour with this endpoint.
In the meantime, as you are migrating to GraphQL already, I would recommend using the GQL Admin API productsCount query instead.
Hi Kellan,
The issue is that the ProductsCount does not have the same functionality as products/count.json
When the graphql request has any parameters attached it returns a max count of 10,000.
For example, if I want to get a count of all published products on a store with over 10,000 published products, it’s wrong. But in theory, I could get a count of all Products (with no query params - which returns the full count) and subtract the unpublished count which is usually under 10,000, but not always… some stores with over 100-200K products can sometimes have tens of thousands of unpublished products.
This is also the case when attaching other types of useful query params and the results are over 10K.
I’ve discussed this in several posts in the last 1 year:
Am I the only developer that experiences these gaps? What does products/count.json have to do with 2048 variants? Wouldn’t the easiest solution be to uncouple the flagging for products/count.json so that we can keep using it without being in violation of some unnecessary rule?
Hi Jason,
I completely understand the concern here and we definitely have had feedback regarding the productCount limitations, and I will be submitting feedback on your behalf internally regarding this as well. I may also suggest you submit feedback yourself as well via the Shopify.dev documentation, scrolling down to the bottom of the page and selecting Was this section helpful?: No, and entering your custom feedback. The more feedback we get on topics like these the more likey and quicker a change will be made, as our developer team does take all feedback into great value when determining future platform updates, changes, and features.
Regarding the products/count.json endpoint being included with the /products and /variants deprecation. This REST deprecation and update with the new Product Model API wasn’t only done for the 2048 variant limit increase project, but was a part of enabling this project to continue, as well as a general update of how products work over all on the platform to enable other updates and platform improvements in the future.
At this time I am still discussing this specific products/count.json endpoint with our developers further to confirm if it is expected that this is included with the deprecations or not, and we will follow up here once we have more information.
Hi @jason_engage,
I’ve discussed this behaviour with our developers further who has confirmed that the products/count.json endpoint is expected to be included in the /products and /variants REST API deprecations.
They also confirmed that the 10,000 return limit with the GraphQL productsCount query is no longer a limitation, and the query should return a full product count on the store.
If you have a new example of a productsCount GQL Admin API query that is still experiencing the limitation, please provide us with the following details and we can help look into it further.
- The full plain text HTTP Request, including URL, Body, and Headers (no access tokens)
- The full plain text HTTP Response, including Body and
x-request-idHeaders
Hi @Kellan-Shopify thanks for the reply
I just discovered that the products count issue has been fixed. And I tested it and it works!
I saw the message in the new DEV DASHBOARD:
**As of GraphQL Admin API version 2025-07, count fields by default stop at 10,000. To retrieve an uncapped count, explicitly set its `limit` argument to `null`.
**
I’ve completely moved over SEO King and Easy Watermarks to GraphQL Products. Sorry for the delay.
I’m getting a TON of messages about an UNSUPPORTED warning message showing up in my merchant admins. Its causing quite a few customer issues. Can you please advise me when the warnings will disappear? We have thousands of merchants using these apps, and in reality the apps were always working just fine, but they made a couple random calls to the products api which I hunted down and totally removed. I understand a temporary demotion, but these unsupported warnings are pretty nasty. I hope you can help with this. Thanks
1 Like
Hi @jason_engage,
Taking a look at your Dev Dashboard, there are a few deprecated calls detected for some of the apps, it does look like they are from the /products and /variants deprecation we were discussing above.
The unsupported warnings will disappear automatically about 3 days after the last detected deprecated call was made. So as long as you’re not calling /products/count.json anymore, or any other /products or /variants REST API calls, the warning banner will disappear in a couple days.
Can you confirm if the current warning banner is actually blocking any installs of your app, or is it just displaying the warning when installing, but the merchant is able to install successfully?
Hi @Kellan-Shopify ,
Thanks for the info about the 72 hour delay. Its been about 60 hours since the last detection.
It’s not blocking installs (probably reducing them though). But existing users (especially members) are seeing it in their admin and messaging us - also perhaps cancelling plans without any message. We added a banner in the app explaining the situation. I understand there are deadlines, but claiming that the app is unsupported when its actually working just fine (and has been the entire time) is pretty drastic. Anyways it looks like it will be cleared up by end of day. Thanks again for getting back to me. Best regards
Hey @jason_engage,
I totally understand how this warning banner can seem drastic when the deprecated calls made are not exactly breaking changes, and I will be submitting some feedback on your behalf internally regarding this.
Please let me know if the banner is not removed after today, and we can look into correcting this further internally.
Hey @jason_engage,
I’m following up here to confirm if the “unsupported” warning banner is still being displayed for your apps after confirming you’ve removed any deprecated calls being made?
If it is now cleared, please let us know and I’ll close this thread as solved. If not, please do give us some more context on what app specifically, and we can definitely help look into it further!
Hi @Kellan-Shopify thanks for the follow up! The unsupported banner is gone. I believe it went away after 72 hours of the last deprecated call. Everything seems back to normal now. Cheers
1 Like