Unable to download salesReports by appstoreconnect api 403 FORBIDDEN_ERROR

Question

chLin20230817 OP

Created Feb ’24

Replies 11

Boosts 6

Views 1.6k

Participants 12

We're using https://api.appstoreconnect.apple.com/v1/salesReports to download salesReports everyday and have been running for 4 years. After 2024/02/22 08:00(GMT+8) the api call started to return 403 error

{ "errors" : [ { "id" : "4e219b15-0d2f-416a-bd66-5c30c314fd44", "status" : "403", "code" : "FORBIDDEN_ERROR", "title" : "This request is forbidden for security reasons", "detail" : "The API key in use does not allow this request" } ] }

we checked our key is still valid, and there's no change about the jwt sign method: https://developer.apple.com/documentation/appstoreconnectapi/generating_tokens_for_api_requests

we tested keys with ADMIN or FINANCE or ACCESS_TO_REPORTS all return the 403 error above.

Boost

Answer 1

gao222 OP

Feb ’24

i meet same question today

1

Answer 2

romulogomes OP

Feb ’24

I'm having the same problem. Have anyone found a solution yet?

1

Answer 3

DanielMueller OP

Feb ’24

We are facing the same problem.

0

Answer 4

JuanEBrainium OP

Feb ’24

I am seeing the same issue here across multiple API keys.

0

Answer 5

mercuryguy OP

Feb ’24

Similar issue, longstanding code running for years suddenly FORBIDDEN

0

Answer 6

Small_black OP

Feb ’24

Same here..... Anyone has any idea how to resolve it

0

Answer 7

RikvanToor OP

Feb ’24

i'm running into the exact same problem. Has anyone found a workaround yet?

0

Answer 8

mwm_ludo OP

Feb ’24

Hello, I will be surprised as if it is not linked to this "App Store Connect update" https://developer.apple.com/news/releases/?id=02222024a

A workaround would be to use the Reporter https://help.apple.com/itc/appsreporterguide/ for now

0

Answer 9

Ado_ OP

Feb ’24

We were having the same issues since Yesterday.

But seems that is working again. I've managed to download the salesReports via the API: https://api.appstoreconnect.apple.com/v1/salesReports

0

Answer 10

Cameron J OP

Feb ’24

It seems to be working now again. At least for me.

0

Answer 11

Edo909 OP

Mar ’24

I'm running in the same issue, is it working again for everyone?

0