URL 404 error on HTTP GET RESTful service

For now, I am keeping this generic. In 2023, the following URL pattern worked:
https://<APIKey>:<API Password>@<Store>.myshopify.com/admin/api/2020-07/orders/count.xml?fulfillment_status=unfulfilled, but now I am getting a 404 error. I have tried version 2025-04, but that also gets the same error. Where can I find such changes documented?

For instance, maybe the following is not supported anymore:

  1. <APIKey>:<API Password>@<Store>
  2. count.xml (not the xml)
    So I guess I am asking where to look for URL pattern changes. Not what is currently supported - that is easy to find. What changed since 2023 supported API versions. I skimmed the rest change log, but did not see anything obvious.

This is a private app. The above is just one example situation, so feel free to use another endpoint if you like. Because it is a private app, the REST API should still be supported, according to what I am seeing.

We are re-enabling and old process, and I am trying to get these scripts working again. Because of time constraints, I am trying to make as few changes as possible, since i know these scripts worked in 2023.

For kicks, I will try to use the X-Shopify-Access-Token HTTP header instead of <APIKey>:<API Password>@, but would still love to figure out where I can see changes, since I have quite a few scripts to go through.

Thanks.

Update: at least in the case of “count.xml”, it looks like that feature might have been deprecated. I wouldn’t mind confirmation on this. Also, if this is true, that is the kind of stuff I need to know. One good thing about change reports is it gives a quick and dirty view of just the changed items, and then we can dig into any issues that concern us. That is what I am looking for, if it is available. Thanks.

Ok, finally found one thing I was looking for here. So it looks like the XML endpoints were deprecated back in 2022. I lucked out in 2023 because I could still use older versions that did support XML. Since those older versions are no longer supported, I guess that effectively removes XML support via the REST API. Is that correct?

Right now I know webhooks can still send XML - I just tested it. Hopefully that won’t change anytime soon. Can someone confirm?

Hey Anthony. Good find. I was just about to link that xml is deprecated.

Regarding REST, it is in legacy mode and the orders count endpoint hasn’t been removed so it should still work using .json

I would recommend switching to Graphql though. There are some great improvements coming in the next release:

What is the quickest way to switch from REST to Graphql? I am in a timecrunch.

That said, so far I think everything I need to do with REST is still supported, minus the XML stuff, but I am double checking each request. So I might be ok for a little while. Something I read suggested it will be a phased out deprecation.

We have a migration guide here that can help with that: About REST to GraphQL migration

With that said, REST is still working minus the XML (like you mentioned), so it wouldn’t need to be an immediate change, but do keep in mind that Graphql is our API technology of choice so you may need to make a change eventually.