Post

Replies

Boosts

Views

Activity

Mapping settled Partner Share to individual subscribers via API
We are integrating with the App Store Connect API to automate ingestion of monthly revenue data for our app (MUBI), and are trying to understand whether there is a report available via the API that provides settled financial data at the individual subscriber level. From our research so far: v1/financeReports with reportType=FINANCE_DETAIL (region Z1) gives us actual settled Partner Share and Extended Partner Share at Transaction Date granularity, but rows are aggregated by SKU + Country + Date, there is no subscriber or individual transaction identifier v1/salesReports with reportType=SUBSCRIBER gives us an anonymised Subscriber ID and Developer Proceeds per billing event, but Developer Proceeds is an estimate using rolling average exchange rates and does not reflect actual settled amounts or withholding tax deductions The App Store Server API (/inApps/v2/history/{transactionId}) provides price and currency per transaction per customer, but requires a transactionId per user, is not designed for bulk analytical pulls, and again does not expose settled Partner Share Is there a report or endpoint we have missed that provides settled Partner Share at the individual subscriber or transaction level? Or is the separation of financial settlement data from subscriber identifiers a deliberate platform decision, e.g. for privacy reasons? Any guidance or suggestions on the recommended approach for reconciling subscriber-level data with actual settled revenue would be much appreciated.
0
1
192
May ’26
Analytics Report Request (ONE_TIME_SNAPSHOT) for historical data retrieval
Hello, I am experiencing an issue with the App Store Connect API where a ONE_TIME_SNAPSHOT analyticsReportRequest appears to be stuck in a ghost state for our app. The issue is as follows: An initial POST to /v1/analyticsReportRequests was made successfully on Thursday 1st May 2026, returning request ID A subsequent GET to /v1/analyticsReportRequests/ returns: Status: 404 NOT_FOUND Detail: "There is no resource of type 'analyticsReportRequests' with id" However, a new POST to /v1/analyticsReportRequests returns: Status: 409 STATE_ERROR Detail: "You already have such an entity" A GET to /v1/apps/626148774/analyticsReportRequests?filter[accessType]=ONE_TIME_SNAPSHOT returns: Status: 200 OK data: [] (empty — total: 0) This is contradictory — the API simultaneously reports that the request does not exist (404) and that it already exists (409), while the app-level listing confirms no active requests. This has been ongoing for a week. As a workaround we have created an ONGOING request instead, but we still require the ONE_TIME_SNAPSHOT to be unblocked for historical data backfill purposes. Could you please investigate and manually clear this ghost request on your backend? Original POST date: Thursday 1st May 2026 Thank you!
2
0
240
May ’26
Receiving full list of Analytics Reports via the App Store Connect API
Hi all, I made an initial ONGOING POST request to the Analytics Reports API, received a request ID, and used it to list available reports. I've waited beyond the documented 24–48 hour generation window, but I'm not seeing the two subscription reports I need from the Commerce category: Subscription State Subscription Event Interestingly, the other three Commerce reports are available (both standard and detailed): App Store Purchases App Store Pre-Orders App Downloads Does the absence of the subscription reports indicate they're not enabled for this account? If so, is there a separate step required to make them available? Thanks
0
0
207
May ’26
Mapping settled Partner Share to individual subscribers via API
We are integrating with the App Store Connect API to automate ingestion of monthly revenue data for our app (MUBI), and are trying to understand whether there is a report available via the API that provides settled financial data at the individual subscriber level. From our research so far: v1/financeReports with reportType=FINANCE_DETAIL (region Z1) gives us actual settled Partner Share and Extended Partner Share at Transaction Date granularity, but rows are aggregated by SKU + Country + Date, there is no subscriber or individual transaction identifier v1/salesReports with reportType=SUBSCRIBER gives us an anonymised Subscriber ID and Developer Proceeds per billing event, but Developer Proceeds is an estimate using rolling average exchange rates and does not reflect actual settled amounts or withholding tax deductions The App Store Server API (/inApps/v2/history/{transactionId}) provides price and currency per transaction per customer, but requires a transactionId per user, is not designed for bulk analytical pulls, and again does not expose settled Partner Share Is there a report or endpoint we have missed that provides settled Partner Share at the individual subscriber or transaction level? Or is the separation of financial settlement data from subscriber identifiers a deliberate platform decision, e.g. for privacy reasons? Any guidance or suggestions on the recommended approach for reconciling subscriber-level data with actual settled revenue would be much appreciated.
Replies
0
Boosts
1
Views
192
Activity
May ’26
Analytics Report Request (ONE_TIME_SNAPSHOT) for historical data retrieval
Hello, I am experiencing an issue with the App Store Connect API where a ONE_TIME_SNAPSHOT analyticsReportRequest appears to be stuck in a ghost state for our app. The issue is as follows: An initial POST to /v1/analyticsReportRequests was made successfully on Thursday 1st May 2026, returning request ID A subsequent GET to /v1/analyticsReportRequests/ returns: Status: 404 NOT_FOUND Detail: "There is no resource of type 'analyticsReportRequests' with id" However, a new POST to /v1/analyticsReportRequests returns: Status: 409 STATE_ERROR Detail: "You already have such an entity" A GET to /v1/apps/626148774/analyticsReportRequests?filter[accessType]=ONE_TIME_SNAPSHOT returns: Status: 200 OK data: [] (empty — total: 0) This is contradictory — the API simultaneously reports that the request does not exist (404) and that it already exists (409), while the app-level listing confirms no active requests. This has been ongoing for a week. As a workaround we have created an ONGOING request instead, but we still require the ONE_TIME_SNAPSHOT to be unblocked for historical data backfill purposes. Could you please investigate and manually clear this ghost request on your backend? Original POST date: Thursday 1st May 2026 Thank you!
Replies
2
Boosts
0
Views
240
Activity
May ’26
Receiving full list of Analytics Reports via the App Store Connect API
Hi all, I made an initial ONGOING POST request to the Analytics Reports API, received a request ID, and used it to list available reports. I've waited beyond the documented 24–48 hour generation window, but I'm not seeing the two subscription reports I need from the Commerce category: Subscription State Subscription Event Interestingly, the other three Commerce reports are available (both standard and detailed): App Store Purchases App Store Pre-Orders App Downloads Does the absence of the subscription reports indicate they're not enabled for this account? If so, is there a separate step required to make them available? Thanks
Replies
0
Boosts
0
Views
207
Activity
May ’26