According to this webpage, reportType: SUBSCRIPTION_EVENT only supports frecuency DAILY at version 1_3 ; doesn't support fecuency MONTHLY. But you can get more days if you use the filter[reportDate] parameter and, by code, iterate over a date range. https://api.appstoreconnect.apple.com/v1/salesReports?filter\[reportDate\]=2021-11-01&filter[frequency]=DAILY&filter[reportSubType]=SUMMARY&filter[reportType]=SUBSCRIPTION_EVENT&filter[vendorNumber]=*****&filter[version]=1_3

According to this webpage, reportType: SUBSCRIPTION_EVENT only supports frecuency DAILY at version 1_3; doesn't support fecuency MONTHLY. But you can get more days if you use the filter[reportDate] parameter and, by code, iterate over a date range. https://api.appstoreconnect.apple.com/v1/salesReports?filter\[reportDate\]=2021-11-01&filter[frequency]=DAILY&filter[reportSubType]=SUMMARY&filter[reportType]=SUBSCRIPTION_EVENT&filter[vendorNumber]=*****&filter[version]=1_3

Hi! I have the same issue, the numbers from the API don't match with those from the App Store Connect website. In my case, it's with Activations and Reactivations from the sales report. And it started happening a couple of months ago; it didn't happen before. If you find any solution or news, please let me know. I'll keep you posted if I learn anything

After analyzing extensively, we realized that there is an issue with the time zone difference. When I request the API to bring me information for the date 09/01/2024, according to my timezone (UTC-3), it even retrieves data with 'event_date=08/01/2024' but with another timezone smaller than mine (UTC -8, for example). If I consider those data points, the API vs. WEB comparison becomes consistent. So you have to consider the time zone for requests by date in the Store Connect API.

I also have this error with Financial Role. It was working as expected until feb 21th 2023 at 8 pm gmt -3. After that, I receive b'{\n "errors" : [ {\n "id" : "xxxxxxx",\n "status" : "403",\n "code" : "FORBIDDEN_ERROR",\n "title" : "This request is forbidden for security reasons",\n "detail" : "The API key in use does not allow this request"\n } ]\n}' the response header is something like this {'Server': 'daiquiri/3.0.0', 'Date': 'Thu, 22 Feb 2024 20:41:42 GMT', 'Content-Type': 'application/json', 'Content-Length': '259', 'Connection': 'keep-alive', 'requestId': 'xxxxx', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains', 'X-Frame-Options': 'SAMEORIGIN', 'X-Request-ID': 'xxxxxx', 'X-Rate-Limit': 'user-hour-lim:3600;user-hour-rem:3599;', 'X-Apple-Jingle-Correlation-Key': 'xxxxxx', 'x-daiquiri-instance': 'daiquiri:xxxxxxx:daiquiri-amp-all-shared-ext-001-pv'} After creating a new api key also with Finance Role, same code with the new key, the error is different b'{\n\t"errors": [{\n\t\t"status": "401",\n\t\t"code": "NOT_AUTHORIZED",\n\t\t"title": "Authentication credentials are missing or invalid.",\n\t\t"detail": "Provide a properly configured and signed bearer token, and make sure that it has not expired. Learn more about Generating Tokens for API Requests https://developer.apple.com/go/?id=api-generating-tokens"\n\t}]\n}' the report being retrieved is present (I have already downloaded it by web). Any ideas?

It's back, lets undo all the "fixes"!

Same here since yesterday