Ok, I'm now noticing 404's coming back from an API call that has worked for years now. Specifically this is the error:
"errors" : [ {
"id" : "90b84655-8c76-4647-b59c-e3bf357793ef",
"status" : "404",
"code" : "PATH_ERROR",
"title" : "The URL path is not valid",
"detail" : "The resource 'v1/appPriceSchedules' does not exist"
} ]
Now I know this error has to be false because in the documentation here if you view the sample response and look at "manualPrices" it has the exact URL that I am calling (with a different appID of course)
"manualPrices" : {
"links" : {
"self" : "https://api.appstoreconnect.apple.com/v1/appPriceSchedules/6447402192/relationships/manualPrices",
"related" : "https://api.appstoreconnect.apple.com/v1/appPriceSchedules/6447402192/manualPrices"
}
},
So can you explain why I'm now getting a 404 for this? Did something break on your end?
Also, why are all of the deprecated endpoints in the API (that are specifically "v1") being replaced with endpoints that also contain "v1" in the URL? Best practice would be to make a "v2" for the new endpoint, then deprecate, then remove the "v1". I really hope you guys aren't just actively "upgrading" the v1 API in place because that's beginner level server development and it's a HUGE pain for your API users.