I'm following the flow to get my reports data:
- get the requests (ONGOING or ONE_TIME_SNAPSHOT) for my app (
https://api.appstoreconnect.apple.com/v1/apps/{{appID}}/analyticsReportRequests?filter%5BaccessType%5D=ONGOING
) - get the report (App Sessions Standard, for example) (
https://api.appstoreconnect.apple.com/v1/analyticsReportRequests/{{requestID}}/reports?filter%5Bname%5D={{report}}
) - get the daily instances of the ONGOING request (
https://api.appstoreconnect.apple.com/v1/analyticsReports/{{reportID}}/instances?filter%5Bgranularity%5D=DAILY
) - get the segments for the selected instance (
https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/{{instanceID}}/segments
)
This flow used to work fine, but recently I noticed that the earliest instances (mostly of processing date 2025-02-24
until 2025-02-27
return an error when I'm trying to get the instance segments usint the URL https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/{{instanceID}}/segments
.
The error is the following:
"title": "The specified resource does not exist", "detail": "There is no resource of type 'analyticsReportInstances' with id '32f8b58b-07da-4d50-899f-34a7c0488927'"
Even when the list of instances return me such object with ID when consulting the resource https://api.appstoreconnect.apple.com/v1/analyticsReports/{{reportID}}/instances?filter%5Bgranularity%5D=DAILY
:
{ "data": [ { "type": "analyticsReportInstances", "id": "32f8b58b-07da-4d50-899f-34a7c0488927", "attributes": { "granularity": "DAILY", "processingDate": "2025-02-25" }, "relationships": { "segments": { "links": { "self": "https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/32f8b58b-07da-4d50-899f-34a7c0488927/relationships/segments", "related": "https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/32f8b58b-07da-4d50-899f-34a7c0488927/segments" } } }, "links": { "self": "https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/32f8b58b-07da-4d50-899f-34a7c0488927" } },
And as for the days that I can retrieve data, there seems to be happening an Internal Server Error with frequency, but retrying the request seems to solve it.