App Store Connect API

RSS for tag

The App Store Connect API helps you automate tasks usually done on the Apple Developer website and App Store Connect.

App Store Connect API Documentation

Posts under App Store Connect API subtopic

Post

Replies

Boosts

Views

Activity

App Store Connect API returns 401 NOT_AUTHORIZED on new account — key never "Last Used"
I enrolled in the Apple Developer Program (individual) in late October 2026. Membership is active and paid. Every App Store Connect API request has returned 401 NOT_AUTHORIZED since I created my key. Details: Key: "OnTask build", Admin access, shows Active (created Nov 7, 2026) Key ID QQH77RTFA9, Issuer ID f2e57319-c56f-4b37-8d5f-90f3b2282d35 The JWT is built and verified with two independent implementations (PyJWT with the ES256 algorithm, and a manual openssl ES256 signing path) — both get the same 401 The key's "Last Used" on Users and Access → Integrations → App Store Connect API has never updated past the creation date, despite repeated authenticated attempts The 401 responses carry no X-Request-ID header and no rate-limit headers I saw the earlier thread describing this exact behavior on a new account ("All App Store Connect API keys return 401 NOT_AUTHORIZED on a new account — 'Last Used' never populates"), and my account shows the identical fingerprint I'm trying to set up CI (GitHub Actions) to build my app and upload it to TestFlight, which is blocked by this. Developer Support case 30000012596548 (filed Nov 11, 2026) has not received a response. Could someone from Apple check whether the App Store Connect API entitlement is provisioned for my account? Thank you.
0
0
42
3d
AppAssetLibraryPlacementState documentation is outdated
I'm following the guide Migrating to the App Asset Library to replace the deprecated app screenshot and preview API with the new app asset library API. Only it seems that the documentation for this new API is already outdated. Specifically, when creating new placements, I get a AppAssetLibraryPlacementsResponse where the state can be ACTIVE, PENDING or INVALID, but the documentation for AppAssetLibraryPlacementState doesn't mention any of these values. For reference, I'm using appstoreconnect-swift-sdk which creates Swift code from the API specification.
2
0
116
3d
ONE_TIME_SNAPSHOT Analytics Report Returns 0 Instances for Both Standard and Detailed Reports (stoppedDueToInactivity: false)
I'm experiencing an issue with the App Store Connect Analytics Reports API where a ONE_TIME_SNAPSHOT report request consistently returns zero report instances (for both Standard and Detailed reports) even though the request itself appears to be valid and active. I want to emphasize: this is not a privacy threshold issue. The problem affects Standard reports, which should not be subject to the same thresholding restrictions as Detailed reports. Environment: API: App Store Connect API Endpoint chain: /v1/analyticsReportRequests → /v1/analyticsReportRequests/{id}/reports → /v1/analyticsReports/{id}/instances Authentication: JWT with Admin role, App Manager scope Reproducibility: 100% — tested across multiple report categories, both Standard and Detailed What I Did: Created a ONE_TIME_SNAPSHOT report request via POST /v1/analyticsReportRequests. The request was accepted and returned successfully: { "data": { "type": "analyticsReportRequests", "id": "4431f553-1091-481a-8312-a2de920df806", "attributes": { "accessType": "ONE_TIME_SNAPSHOT", "stoppedDueToInactivity": false } } } I then fetched the available reports under this request via GET /v1/analyticsReportRequests/4431f553-1091-481a-8312-a2de920df806/reports, which returned multiple report objects. For example: { "data": [ { "type": "analyticsReports", "id": "r15-4431f553-1091-481a-8312-a2de920df806", "attributes": { "name": "App Store Discovery and Engagement Detailed", "category": "APP_STORE_ENGAGEMENT" } } ] } When I try to fetch the actual report instances via GET /v1/analyticsReports/r15-4431f553-1091-481a-8312-a2de920df806/instances, I consistently get an empty response I also tried the Standard version of the same report — "App Store Discovery and Engagement Standard" — and the result is identical: zero instances returned. This rules out Apple's privacy thresholds as the cause, since Standard reports are not subject to the same minimum-user thresholding that Detailed reports are. What I Expected: At least one report instance with a processingDate and a downloadable URL, since the report request is active (stoppedDueToInactivity is false) and was created as a ONE_TIME_SNAPSHOT. Troubleshooting I've Already Done: Waited 24–48 hours after creating the report request before polling for instances, as the documentation suggests data may not be immediately available. Verified the app has active downloads and engagement data (the app is live on the App Store with steady traffic). Tried multiple report categories under the same request (not just APP_STORE_ENGAGEMENT) — all return 0 instances. Tested both Standard and Detailed report variants — both return empty instances, confirming this is not a privacy threshold issue. Created entirely new ONE_TIME_SNAPSHOT requests on different days — same result. Confirmed the JWT token has the correct role and permissions. Verified via GET /v1/analyticsReportRequests that the request status shows stoppedDueToInactivity: false, ruling out an expired or inactive request. Tested with both filtered and unfiltered instance queries (with and without filter[processingDate] and filter[granularity] parameters). Questions: Is there a known delay or prerequisite before ONE_TIME_SNAPSHOT instances become available beyond the ~24 hours mentioned in the docs? Could this be a backend issue where snapshot generation is silently failing without surfacing an error? Are there minimum data thresholds an app must meet before Standard report instances are generated? I've seen several other developers reporting identical symptoms in these forums, across both Standard and Detailed reports, and across both ONE_TIME_SNAPSHOT and ONGOING request types — with no resolution so far. Any insight from Apple engineers would be greatly appreciated. Happy to provide additional request/response logs if needed. Thanks in advance.
3
2
1.1k
1w
Has anyone had any issues submitting apps via the API for review? Is this discouraged?
Hi, I submitted my latest games using the API at the weekend because there were two of them and they were cross platform ( tvos, ios and mac ) and doing it by hand takes a lot of time. These apps have now been rejected as spam apps ( they are fully fledged original concept games, one being a 2.0 of an app already live ). I have appealed but does submitting via the API trigger a red flag? Has anyone had any issues with this? I'd like to know for next time, as this will now introduce a marketing delay.
0
0
50
1w
App Store Connect API - Installs/Deletes discrepencies with Analytics
Hi, I have a question about the numbers that we get from using the App Store Connect API and what is visible through Metrics/Analytics in App Store Connect's UI. Specifically, there appears to be significant discrepencies between counts for downloads, installs, deletes when comparing both data sets. I would expect them to be the same. Our workflow: Run app_installs_deletes through the API and download the provided report from the URL received Run Analytics, Total Downloads, through App Store Connect website In my case, running this for a day well in the past (to cater for catch up processing time), for example 20th Sept 2026, I get 37622 total downloads from the ASC website, but 21190 from the report data. This is a significant difference. What specific API report should be run to get the same data as displasy in App Store Connect? Looking to ensure that I have exact number from the ASC analytics/metrics, through an API report, on Installs, Updates, Deletes, Downloads. Any help appreciated. Developer support pointed me to post in the forums...
0
0
98
2w
Cloud-Based App Builder: Rules for Automated App Store Submission on Behalf of Users
Hello everyone, I'm building a cloud-based AI mobile app development platform called TryAppnetic (https://tryappnetic.com), where users can generate React Native/Expo applications and publish them under their own Apple Developer accounts. I'm currently researching how to implement automated iOS app publishing and have some questions regarding the Apple Developer Program License Agreement. Specifically, Section 2.9 appears to restrict third-party service providers from submitting applications to the App Store or using TestFlight on behalf of developers. Section 5.1 also introduces restrictions around certificates and private keys. I'd like to understand what is technically and legally permitted for a platform like ours. Our intended workflow: A user generates an iOS application using our platform. We build the application in our cloud infrastructure. The user authorizes access to their Apple Developer account. We use authorized credentials or App Store Connect API keys to manage the build and upload process. The application is published under the user's own Apple Developer account. My questions: Is it permitted for a cloud-based platform to build and compile iOS applications on behalf of users? Can we automate code signing using certificates and provisioning profiles belonging to the user, provided they explicitly authorize their use? Can we use customer-generated App Store Connect API keys to automate uploading builds to App Store Connect? Does Section 2.9 prohibit automated build uploads as well, or does it specifically prohibit the actual submission of an app for App Store review and TestFlight distribution? Would it be compliant to automate the entire build and upload process but leave the final App Store submission and TestFlight distribution actions to the account owner? I'm particularly interested in hearing from developers who have built cloud-based development platforms, CI/CD services, or automated iOS publishing workflows. I'd also appreciate clarification from anyone familiar with Apple's interpretation of Sections 2.9 and 5.1. Thanks!
0
0
85
2w
XmasMaps (Team ID: 34WAQXFJHP) Stuck in "Waiting for Review"
To Apple Engineers, I don't seem to get any updates or responses so I will keep trying to reach out here. Please work with me on what is needed to get my app approved. it is truly important to get it deployed as soon as we can so I can begin to launch and promote the app in App Store. It has already been live on the Google Play Store for a couple weeks. My app: XmasMaps has been going from "Waiting for Review" to "Rejected". I would fix the mistakes right away which would put XmasMaps back into "Waiting for Review". This App would be a useless App after November. Our app, XmasMaps, has been stuck in "Waiting for Review" since September 29th, 2026 (Submission ID: 1ced2377-575b-4bdd-812f-2852a23c2ffc). Timeline of previous actions: Sept 29, 2026: Initial submission Oct 8 & Oct 11, 2026: Resubmitted fixes following rejections Oct 14, 2026: new build resubmitted, currently stuck in "Waiting for Review" Oct 16, 2026: Expedited review request submitted Oct 19, 2026: Support customer inquiry submitted Android is already live, and we are hoping to clear iOS review so users can access the platform ahead of the upcoming holiday season. Oct 24, 2026: Rejected again for something already built into my latest build. i resubmitted right away and now put back into "waiting for review" when I would expect that the engineer who rejected it would take it back and finalize my app. Oct 28, 2026: As of today, I opened multiple app requests for an update and update the forum multiple times until I can try to get a response. Submission ID: 1ced2377-575b-4bdd-812f-2852a23c2ffc Support Case ID: 102982950152 / 103008467960 Team ID: 34WAQXFJHP I ask, please assist and review my app. I really need it live on both platforms to promote it. Please let me know if any additional information is needed from my side. Thank you.
1
0
247
2w
Sandbox subscription purchase fails with ASDServerErrorDomain 3504
Type: Auto-renewable subscription Sandbox Storefront: USA StoreKit successfully loads the subscription product and returns its correct name and price (US$29.99). However, every purchase attempt fails: ASDServerErrorDomain Code=3504 AMSServerErrorCode=3504 "Item not found" client-environment-type=Sandbox storefront-country-code=USA This reproduces both in a TestFlight build and in iPhone Developer Settings > Test In-App Purchases. Please verify the app-product linkage and Sandbox commerce availability for this subscription product. Purchase did not return a transaction: Error Domain=ASDServerErrorDomain Code=3504 "找不到此项目。" UserInfo={storefront-country-code=USA, AMSServerErrorCode=3504, client-environment-type=Sandbox, NSLocalizedFailureReason=找不到此项目。} HKIPO-IAP 11:12:33.712 purchase error: type=StoreKit.Product.PurchaseError, domain=StoreKit.Product.PurchaseError, code=1, description=無法使用項目, failureReason=目前無法使用此項目。, underlying=nil, userInfo={}
1
1
892
2w
Receipt validation: Under what circumstances can receipt.in_app be empty after a successful consumable purchase?
Hi everyone, I'm investigating an issue related to StoreKit 1 receipt validation and would appreciate any insight from Apple engineers or developers who have encountered this before. Environment StoreKit 1 Consumable In-App Purchase iOS 16 / iOS 17 / iOS 18 (observed on multiple versions) Receipt validation performed on our server Receipt is read from the app bundle after the transaction completes Issue Occasionally, after a purchase succeeds and the transaction reaches the SKPaymentTransactionStatePurchased state, the App Receipt exists and can be decoded successfully, but the receipt contains: { "receipt": { ... "in_app": [] } } The in_app array is completely empty. As a result, our server cannot find the purchased product in the receipt and cannot complete receipt validation. Questions I'd like to understand under what circumstances Apple may return an App Receipt where receipt.in_app is empty. Specifically: Is it expected behavior that receipt.in_app can be empty after a successful consumable purchase? Could this happen if the app reads the receipt before the receipt has been updated? Is there any possibility that calling finishTransaction: before reading the receipt could cause the purchase record not to appear in receipt.in_app? If receipt synchronization is delayed, what is Apple's recommended approach? Wait and retry? Issue an SKReceiptRefreshRequest? Or validate using another mechanism? Are there any documented scenarios where Apple intentionally returns an empty in_app array? Additional Information The transaction state is Purchased. The purchase callback is received successfully. We have confirmed that the receipt file exists. The issue occurs only occasionally and cannot be reproduced consistently. Most purchases contain the expected in_app entry. Any clarification about the expected behavior of the App Receipt or recommended best practices would be greatly appreciated. Thank you!
1
0
829
3w
Testing Declared Age Range API on Production
Hello, We want to ensure that our Declared Age Range API is working correctly, in Production, but we had concerns on how this is done. Do we need to have an account created from Texas with a credit card/addressed based in Texas? What's the best approach to be able to test this in a live environment to ensure everything is working as intended? Thank You.
0
0
47
3w
Create app in Appstore using AppStoreConnect API is giving an error.
Hello Apple Developer Team, I've followed the AppStoreConnect API documentation and created the following: I've created a API Key in App store > Integrations > Teams key, gave the role as admin. Created a valid JWT token When fetching the GET v1/apps, I can see the list of apps. Also I was able to make GET v1/users as well successfully. I've the valid bundle Id and capabilities enabled in the developer portal. Facing an issue while creating an app in App Store using AppStoreConnect API using POST call: This is my ruby script: response = api_request( method: :post, path: "/v1/apps", token: token, body: { data: { type: 'apps', attributes: { name: APP_NAME, primaryLocale: LOCALE, sku: "SKU#{Time.now.to_i}", bundleId: BUNDLE_ID, platform: 'IOS' } } } ) It gives me below error: { "errors": [ { "id": "09b465fc-316f-47b4-9bc3-9c340cb966aa", "status": "403", "code": "FORBIDDEN_ERROR", "title": "The given operation is not allowed", "detail": "The resource 'apps' does not allow 'CREATE'. Allowed operations are: GET_COLLECTION, GET_INSTANCE, UPDATE" } ] } Did anyone was able to successfully create the app in App Store via AppStoreConnect API? Could you please help me identify the root cause for the above issue and provide some inputs so that I could work on resolving them and move forward in the deployment process. Appreciate your help in reviewing this. Thank you, Santosh
3
1
1.4k
3w
No App Store Connect API endpoint to associate a Bundle ID with an Apple Pay Merchant ID
We manage provisioning for a large number of App IDs across multiple apps via CI, using the App Store Connect API (not session-based Spaceship/Xcode auth). Capability management works well end to end for everything we've tried — Push Notifications, App Groups, Associated Domains, Data Protection, etc. can all be created, updated, and deleted via POST/PATCH/DELETE on /v1/bundleIdCapabilities. Apple Pay is the one exception. We can enable the Apple Pay capability itself via the API the same way as anything else, but there's no way to associate that capability with a specific Merchant ID. /v1/merchantIds exists as its own resource, but nothing in the bundleIdCapabilities or bundleIds schema links to it — no relationship, no include, no dedicated endpoint. In practice this means every new Apple Pay-enabled App ID we provision needs someone to go into the Developer Portal by hand (Identifiers → App ID → Capabilities → Apple Pay → select Merchant ID) before the generated provisioning profile will actually build — otherwise Xcode fails with errors like "doesn't include the Apple Pay capability" / "doesn't support the Merchant ID". Every other capability we use is fully scriptable; this is the one manual step left in an otherwise automated pipeline. Has anyone found a documented (or undocumented) way to do this via the API? If this is a confirmed gap rather than something we're missing, I've filed it as FB24414090 — if you've hit the same thing, adding your own Feedback number to a report on the same gap seems to be one of the few things that actually helps get traction internally, so feel free to reference this thread if you file one too.
2
0
800
3w
Getting Active Devices via the API?
I am trying to retrieve the numbers displayed in "App Analytics" under "Metrics" > "Active Devices" using the API. Since there does not seem to be a dedicated report for this metric I am using the daily "App Sessions Standard" report and by looking at the "Sessions" field I am able to recreate the numbers displayed for the "Sessions" metric. However if I try to infer the active devices by looking at the "Unique Devices" field my numbers for individual days are in the same ballpark (deviations may be attributable to privacy reasons?), but the total number of devices is way off. Is there a better way to recreate this metric?
2
2
536
3w
I hooked an AI up to App Store Connect, Meta Ads, and Firebase via official APIs. It is a marketing monster, but does this violate Apple's TOS?
Today I witnessed the real power of AI beyond just writing code. I am using it as a super marketer to drive up my app business, and the results are incredible. This is what I have set up. I provided read access to the AI using their official APIs for: App Store Connect Apple Search Ads Meta Ads Firebase Analytics Local app source code By combining the source code with real performance data, the AI ran a thorough analysis and suggested concrete, actionable items to improve my overall app business. My main concern is whether this is allowed by Apple. Specifically, does Apple permit using AI agents to query App Store Connect and Apple Search Ads through their official APIs? The setup is too powerful not to use, but we still need to abide by Apple rules. Has anyone else looked into this or tried a similar workflow?
1
0
273
Oct ’26
How to specify dimensions in App Analytics reports API?
I'm fetching Apple Store Connect data from the API (in particular, fetching the App Store Purchases report) and trying to replicate the dashboards that we can see under Analytics > Metrics. The thresholding that Apple applies ("Omits values with data from fewer than 5 users or 5 unique devices") means that a lot of data is lost. Is there a way of specifying the dimensions of the report? If we had less dimensions, the threshold would affect to less rows of data, and we would be able to analyze more data. It's strange that from the website of App Store Analytics we can get the data, but through the automated reports we cannot or a lot of data is lost due to not being able to set the report dimensions.
2
0
647
Oct ’26
Request for a supported endpoint to create apps (POST /v1/apps)
We are requesting a supported App Store Connect API endpoint for creating a new app record, for example POST /v1/apps. We run an automated "create app" workflow that sets up new apps as part of our app management service. The App Store Connect API supports reading and updating apps, but the Apps documentation (https://developer.apple.com/documentation/appstoreconnectapi/apps) lists no way to create one. A new app can only be created on the App Store Connect website. Today our approach is using a third-party library (fastlane's Spaceship) that calls the private endpoints behind the App Store Connect website. Those endpoints can change at any time, and if they do, app creation and our automation will stop working. A supported endpoint, authenticated with an App Store Connect API key, would let us create apps reliably. Thank you for considering this request.
0
1
186
Oct ’26
App Store Connect API authorization for Game Center player score and achievement submissions
We are calling these App Store Connect API endpoints from our server: curl --request POST \ --url https://api.appstoreconnect.apple.com/v1/gameCenterLeaderboardEntrySubmissions \ --header 'Authorization: Bearer JWT_Token' \ --header 'Content-Type: application/json' \ --data '{ "data": { "type": "gameCenterLeaderboardEntrySubmissions", "attributes": { "bundleId": "bundleId", "score": "1", "scopedPlayerId": "scopedPlayerId, "submittedDate": "date", "preReleased": true, "vendorIdentifier": "vendorIdentifier" } } }' curl --request POST \ --url https://api.appstoreconnect.apple.com/v1/gameCenterPlayerAchievementSubmissions \ --header 'Authorization: Bearer JWT_Token' \ --header 'Content-Type: application/json' \ --data '{ "data": { "type": "gameCenterPlayerAchievementSubmissions", "attributes": { "bundleId": "bundleId", "vendorIdentifier": "vendorIdentifier", "percentageAchieved": 1, "scopedPlayerId": "scopedPlayerId, "submittedDate": "Date", "preReleased": true } } }' According to https://developer.apple.com/documentation/appstoreconnectapi/app-store-connect-api-3-2-release-notes We should be able to set player score and achievements. We use an active Team App Store Connect API key and generate an unscoped ES256 JWT with aud: appstoreconnect-v1. The key has high-level App Store Connect permissions. We followed documentation: https://developer.apple.com/documentation/appstoreconnectapi https://developer.apple.com/documentation/appstoreconnectapi/post-v1-gamecenterplayerachievementsubmissions https://developer.apple.com/documentation/appstoreconnectapi/post-v1-gamecenterleaderboardentrysubmissions Both requests return: { "status": "403", "code": "FORBIDDEN_ERROR", "title": "This request is forbidden for security reasons", "detail": "The API key in use does not allow this request" } The player is authorised via GameKit on the mobile app. The API key can read: https://api.appstoreconnect.apple.com/v1/apps/:id https://api.appstoreconnect.apple.com/v2/gameCenterLeaderboards/:id. Which exact App Store Connect API key role or permission is required for these endpoints? Is server-to-server submission supported using a Team API key?
0
0
195
Oct ’26
App Store Connect Metrics via REST API
I hope this message finds you well. I’m reaching out to ask whether specific App Store Connect metrics available in the App Analytics dashboard can also be accessed via the App Store Connect REST API. I have reviewed the official API documentation, but I couldn’t find confirmation regarding the metrics listed below. Could you kindly clarify if the following metrics are available through the REST API? And if so, could you point me to the relevant endpoints or documentation? From the "Usage" group: Installations (Opt-in only) Active Devices Deletions (Uninstalls) From the "App Store" group: Impressions (Unique Devices) Product Page Views (Unique Devices) If these metrics are not available via the REST API, is there an alternative method to programmatically access or export them? Thank you very much in advance for your help and guidance.
5
3
1.8k
Oct ’26
Unable to download App Store Connect API keys in iOS Safari
Posting here to see if anyone has found a workaround and/or to get Apple employees' eyes on it. I'm not sure when this bug was introduced but I've found that in Safari on iOS 27, I'm unable to download API keys from App Store Connect. Reported as a Safari bug in Feedback Assistant (FB24994724). I checked web inspector's console and network logs for both my iPad and iPhone; no JS errors and a nondescript network error for the key's fetch request. Google Chrome for iPad/iPhone downloads the .p8 key file without issue, so this feels more like a Safari bug than an App Store Connect bug.
0
0
356
Sep ’26
App Store Connect API returns 401 NOT_AUTHORIZED on new account — key never "Last Used"
I enrolled in the Apple Developer Program (individual) in late October 2026. Membership is active and paid. Every App Store Connect API request has returned 401 NOT_AUTHORIZED since I created my key. Details: Key: "OnTask build", Admin access, shows Active (created Nov 7, 2026) Key ID QQH77RTFA9, Issuer ID f2e57319-c56f-4b37-8d5f-90f3b2282d35 The JWT is built and verified with two independent implementations (PyJWT with the ES256 algorithm, and a manual openssl ES256 signing path) — both get the same 401 The key's "Last Used" on Users and Access → Integrations → App Store Connect API has never updated past the creation date, despite repeated authenticated attempts The 401 responses carry no X-Request-ID header and no rate-limit headers I saw the earlier thread describing this exact behavior on a new account ("All App Store Connect API keys return 401 NOT_AUTHORIZED on a new account — 'Last Used' never populates"), and my account shows the identical fingerprint I'm trying to set up CI (GitHub Actions) to build my app and upload it to TestFlight, which is blocked by this. Developer Support case 30000012596548 (filed Nov 11, 2026) has not received a response. Could someone from Apple check whether the App Store Connect API entitlement is provisioned for my account? Thank you.
Replies
0
Boosts
0
Views
42
Activity
3d
AppAssetLibraryPlacementState documentation is outdated
I'm following the guide Migrating to the App Asset Library to replace the deprecated app screenshot and preview API with the new app asset library API. Only it seems that the documentation for this new API is already outdated. Specifically, when creating new placements, I get a AppAssetLibraryPlacementsResponse where the state can be ACTIVE, PENDING or INVALID, but the documentation for AppAssetLibraryPlacementState doesn't mention any of these values. For reference, I'm using appstoreconnect-swift-sdk which creates Swift code from the API specification.
Replies
2
Boosts
0
Views
116
Activity
3d
ONE_TIME_SNAPSHOT Analytics Report Returns 0 Instances for Both Standard and Detailed Reports (stoppedDueToInactivity: false)
I'm experiencing an issue with the App Store Connect Analytics Reports API where a ONE_TIME_SNAPSHOT report request consistently returns zero report instances (for both Standard and Detailed reports) even though the request itself appears to be valid and active. I want to emphasize: this is not a privacy threshold issue. The problem affects Standard reports, which should not be subject to the same thresholding restrictions as Detailed reports. Environment: API: App Store Connect API Endpoint chain: /v1/analyticsReportRequests → /v1/analyticsReportRequests/{id}/reports → /v1/analyticsReports/{id}/instances Authentication: JWT with Admin role, App Manager scope Reproducibility: 100% — tested across multiple report categories, both Standard and Detailed What I Did: Created a ONE_TIME_SNAPSHOT report request via POST /v1/analyticsReportRequests. The request was accepted and returned successfully: { "data": { "type": "analyticsReportRequests", "id": "4431f553-1091-481a-8312-a2de920df806", "attributes": { "accessType": "ONE_TIME_SNAPSHOT", "stoppedDueToInactivity": false } } } I then fetched the available reports under this request via GET /v1/analyticsReportRequests/4431f553-1091-481a-8312-a2de920df806/reports, which returned multiple report objects. For example: { "data": [ { "type": "analyticsReports", "id": "r15-4431f553-1091-481a-8312-a2de920df806", "attributes": { "name": "App Store Discovery and Engagement Detailed", "category": "APP_STORE_ENGAGEMENT" } } ] } When I try to fetch the actual report instances via GET /v1/analyticsReports/r15-4431f553-1091-481a-8312-a2de920df806/instances, I consistently get an empty response I also tried the Standard version of the same report — "App Store Discovery and Engagement Standard" — and the result is identical: zero instances returned. This rules out Apple's privacy thresholds as the cause, since Standard reports are not subject to the same minimum-user thresholding that Detailed reports are. What I Expected: At least one report instance with a processingDate and a downloadable URL, since the report request is active (stoppedDueToInactivity is false) and was created as a ONE_TIME_SNAPSHOT. Troubleshooting I've Already Done: Waited 24–48 hours after creating the report request before polling for instances, as the documentation suggests data may not be immediately available. Verified the app has active downloads and engagement data (the app is live on the App Store with steady traffic). Tried multiple report categories under the same request (not just APP_STORE_ENGAGEMENT) — all return 0 instances. Tested both Standard and Detailed report variants — both return empty instances, confirming this is not a privacy threshold issue. Created entirely new ONE_TIME_SNAPSHOT requests on different days — same result. Confirmed the JWT token has the correct role and permissions. Verified via GET /v1/analyticsReportRequests that the request status shows stoppedDueToInactivity: false, ruling out an expired or inactive request. Tested with both filtered and unfiltered instance queries (with and without filter[processingDate] and filter[granularity] parameters). Questions: Is there a known delay or prerequisite before ONE_TIME_SNAPSHOT instances become available beyond the ~24 hours mentioned in the docs? Could this be a backend issue where snapshot generation is silently failing without surfacing an error? Are there minimum data thresholds an app must meet before Standard report instances are generated? I've seen several other developers reporting identical symptoms in these forums, across both Standard and Detailed reports, and across both ONE_TIME_SNAPSHOT and ONGOING request types — with no resolution so far. Any insight from Apple engineers would be greatly appreciated. Happy to provide additional request/response logs if needed. Thanks in advance.
Replies
3
Boosts
2
Views
1.1k
Activity
1w
Has anyone had any issues submitting apps via the API for review? Is this discouraged?
Hi, I submitted my latest games using the API at the weekend because there were two of them and they were cross platform ( tvos, ios and mac ) and doing it by hand takes a lot of time. These apps have now been rejected as spam apps ( they are fully fledged original concept games, one being a 2.0 of an app already live ). I have appealed but does submitting via the API trigger a red flag? Has anyone had any issues with this? I'd like to know for next time, as this will now introduce a marketing delay.
Replies
0
Boosts
0
Views
50
Activity
1w
App Store Connect API - Installs/Deletes discrepencies with Analytics
Hi, I have a question about the numbers that we get from using the App Store Connect API and what is visible through Metrics/Analytics in App Store Connect's UI. Specifically, there appears to be significant discrepencies between counts for downloads, installs, deletes when comparing both data sets. I would expect them to be the same. Our workflow: Run app_installs_deletes through the API and download the provided report from the URL received Run Analytics, Total Downloads, through App Store Connect website In my case, running this for a day well in the past (to cater for catch up processing time), for example 20th Sept 2026, I get 37622 total downloads from the ASC website, but 21190 from the report data. This is a significant difference. What specific API report should be run to get the same data as displasy in App Store Connect? Looking to ensure that I have exact number from the ASC analytics/metrics, through an API report, on Installs, Updates, Deletes, Downloads. Any help appreciated. Developer support pointed me to post in the forums...
Replies
0
Boosts
0
Views
98
Activity
2w
Cloud-Based App Builder: Rules for Automated App Store Submission on Behalf of Users
Hello everyone, I'm building a cloud-based AI mobile app development platform called TryAppnetic (https://tryappnetic.com), where users can generate React Native/Expo applications and publish them under their own Apple Developer accounts. I'm currently researching how to implement automated iOS app publishing and have some questions regarding the Apple Developer Program License Agreement. Specifically, Section 2.9 appears to restrict third-party service providers from submitting applications to the App Store or using TestFlight on behalf of developers. Section 5.1 also introduces restrictions around certificates and private keys. I'd like to understand what is technically and legally permitted for a platform like ours. Our intended workflow: A user generates an iOS application using our platform. We build the application in our cloud infrastructure. The user authorizes access to their Apple Developer account. We use authorized credentials or App Store Connect API keys to manage the build and upload process. The application is published under the user's own Apple Developer account. My questions: Is it permitted for a cloud-based platform to build and compile iOS applications on behalf of users? Can we automate code signing using certificates and provisioning profiles belonging to the user, provided they explicitly authorize their use? Can we use customer-generated App Store Connect API keys to automate uploading builds to App Store Connect? Does Section 2.9 prohibit automated build uploads as well, or does it specifically prohibit the actual submission of an app for App Store review and TestFlight distribution? Would it be compliant to automate the entire build and upload process but leave the final App Store submission and TestFlight distribution actions to the account owner? I'm particularly interested in hearing from developers who have built cloud-based development platforms, CI/CD services, or automated iOS publishing workflows. I'd also appreciate clarification from anyone familiar with Apple's interpretation of Sections 2.9 and 5.1. Thanks!
Replies
0
Boosts
0
Views
85
Activity
2w
XmasMaps (Team ID: 34WAQXFJHP) Stuck in "Waiting for Review"
To Apple Engineers, I don't seem to get any updates or responses so I will keep trying to reach out here. Please work with me on what is needed to get my app approved. it is truly important to get it deployed as soon as we can so I can begin to launch and promote the app in App Store. It has already been live on the Google Play Store for a couple weeks. My app: XmasMaps has been going from "Waiting for Review" to "Rejected". I would fix the mistakes right away which would put XmasMaps back into "Waiting for Review". This App would be a useless App after November. Our app, XmasMaps, has been stuck in "Waiting for Review" since September 29th, 2026 (Submission ID: 1ced2377-575b-4bdd-812f-2852a23c2ffc). Timeline of previous actions: Sept 29, 2026: Initial submission Oct 8 & Oct 11, 2026: Resubmitted fixes following rejections Oct 14, 2026: new build resubmitted, currently stuck in "Waiting for Review" Oct 16, 2026: Expedited review request submitted Oct 19, 2026: Support customer inquiry submitted Android is already live, and we are hoping to clear iOS review so users can access the platform ahead of the upcoming holiday season. Oct 24, 2026: Rejected again for something already built into my latest build. i resubmitted right away and now put back into "waiting for review" when I would expect that the engineer who rejected it would take it back and finalize my app. Oct 28, 2026: As of today, I opened multiple app requests for an update and update the forum multiple times until I can try to get a response. Submission ID: 1ced2377-575b-4bdd-812f-2852a23c2ffc Support Case ID: 102982950152 / 103008467960 Team ID: 34WAQXFJHP I ask, please assist and review my app. I really need it live on both platforms to promote it. Please let me know if any additional information is needed from my side. Thank you.
Replies
1
Boosts
0
Views
247
Activity
2w
Sandbox subscription purchase fails with ASDServerErrorDomain 3504
Type: Auto-renewable subscription Sandbox Storefront: USA StoreKit successfully loads the subscription product and returns its correct name and price (US$29.99). However, every purchase attempt fails: ASDServerErrorDomain Code=3504 AMSServerErrorCode=3504 "Item not found" client-environment-type=Sandbox storefront-country-code=USA This reproduces both in a TestFlight build and in iPhone Developer Settings > Test In-App Purchases. Please verify the app-product linkage and Sandbox commerce availability for this subscription product. Purchase did not return a transaction: Error Domain=ASDServerErrorDomain Code=3504 "找不到此项目。" UserInfo={storefront-country-code=USA, AMSServerErrorCode=3504, client-environment-type=Sandbox, NSLocalizedFailureReason=找不到此项目。} HKIPO-IAP 11:12:33.712 purchase error: type=StoreKit.Product.PurchaseError, domain=StoreKit.Product.PurchaseError, code=1, description=無法使用項目, failureReason=目前無法使用此項目。, underlying=nil, userInfo={}
Replies
1
Boosts
1
Views
892
Activity
2w
Receipt validation: Under what circumstances can receipt.in_app be empty after a successful consumable purchase?
Hi everyone, I'm investigating an issue related to StoreKit 1 receipt validation and would appreciate any insight from Apple engineers or developers who have encountered this before. Environment StoreKit 1 Consumable In-App Purchase iOS 16 / iOS 17 / iOS 18 (observed on multiple versions) Receipt validation performed on our server Receipt is read from the app bundle after the transaction completes Issue Occasionally, after a purchase succeeds and the transaction reaches the SKPaymentTransactionStatePurchased state, the App Receipt exists and can be decoded successfully, but the receipt contains: { "receipt": { ... "in_app": [] } } The in_app array is completely empty. As a result, our server cannot find the purchased product in the receipt and cannot complete receipt validation. Questions I'd like to understand under what circumstances Apple may return an App Receipt where receipt.in_app is empty. Specifically: Is it expected behavior that receipt.in_app can be empty after a successful consumable purchase? Could this happen if the app reads the receipt before the receipt has been updated? Is there any possibility that calling finishTransaction: before reading the receipt could cause the purchase record not to appear in receipt.in_app? If receipt synchronization is delayed, what is Apple's recommended approach? Wait and retry? Issue an SKReceiptRefreshRequest? Or validate using another mechanism? Are there any documented scenarios where Apple intentionally returns an empty in_app array? Additional Information The transaction state is Purchased. The purchase callback is received successfully. We have confirmed that the receipt file exists. The issue occurs only occasionally and cannot be reproduced consistently. Most purchases contain the expected in_app entry. Any clarification about the expected behavior of the App Receipt or recommended best practices would be greatly appreciated. Thank you!
Replies
1
Boosts
0
Views
829
Activity
3w
Testing Declared Age Range API on Production
Hello, We want to ensure that our Declared Age Range API is working correctly, in Production, but we had concerns on how this is done. Do we need to have an account created from Texas with a credit card/addressed based in Texas? What's the best approach to be able to test this in a live environment to ensure everything is working as intended? Thank You.
Replies
0
Boosts
0
Views
47
Activity
3w
Create app in Appstore using AppStoreConnect API is giving an error.
Hello Apple Developer Team, I've followed the AppStoreConnect API documentation and created the following: I've created a API Key in App store > Integrations > Teams key, gave the role as admin. Created a valid JWT token When fetching the GET v1/apps, I can see the list of apps. Also I was able to make GET v1/users as well successfully. I've the valid bundle Id and capabilities enabled in the developer portal. Facing an issue while creating an app in App Store using AppStoreConnect API using POST call: This is my ruby script: response = api_request( method: :post, path: "/v1/apps", token: token, body: { data: { type: 'apps', attributes: { name: APP_NAME, primaryLocale: LOCALE, sku: "SKU#{Time.now.to_i}", bundleId: BUNDLE_ID, platform: 'IOS' } } } ) It gives me below error: { "errors": [ { "id": "09b465fc-316f-47b4-9bc3-9c340cb966aa", "status": "403", "code": "FORBIDDEN_ERROR", "title": "The given operation is not allowed", "detail": "The resource 'apps' does not allow 'CREATE'. Allowed operations are: GET_COLLECTION, GET_INSTANCE, UPDATE" } ] } Did anyone was able to successfully create the app in App Store via AppStoreConnect API? Could you please help me identify the root cause for the above issue and provide some inputs so that I could work on resolving them and move forward in the deployment process. Appreciate your help in reviewing this. Thank you, Santosh
Replies
3
Boosts
1
Views
1.4k
Activity
3w
No App Store Connect API endpoint to associate a Bundle ID with an Apple Pay Merchant ID
We manage provisioning for a large number of App IDs across multiple apps via CI, using the App Store Connect API (not session-based Spaceship/Xcode auth). Capability management works well end to end for everything we've tried — Push Notifications, App Groups, Associated Domains, Data Protection, etc. can all be created, updated, and deleted via POST/PATCH/DELETE on /v1/bundleIdCapabilities. Apple Pay is the one exception. We can enable the Apple Pay capability itself via the API the same way as anything else, but there's no way to associate that capability with a specific Merchant ID. /v1/merchantIds exists as its own resource, but nothing in the bundleIdCapabilities or bundleIds schema links to it — no relationship, no include, no dedicated endpoint. In practice this means every new Apple Pay-enabled App ID we provision needs someone to go into the Developer Portal by hand (Identifiers → App ID → Capabilities → Apple Pay → select Merchant ID) before the generated provisioning profile will actually build — otherwise Xcode fails with errors like "doesn't include the Apple Pay capability" / "doesn't support the Merchant ID". Every other capability we use is fully scriptable; this is the one manual step left in an otherwise automated pipeline. Has anyone found a documented (or undocumented) way to do this via the API? If this is a confirmed gap rather than something we're missing, I've filed it as FB24414090 — if you've hit the same thing, adding your own Feedback number to a report on the same gap seems to be one of the few things that actually helps get traction internally, so feel free to reference this thread if you file one too.
Replies
2
Boosts
0
Views
800
Activity
3w
Getting Active Devices via the API?
I am trying to retrieve the numbers displayed in "App Analytics" under "Metrics" > "Active Devices" using the API. Since there does not seem to be a dedicated report for this metric I am using the daily "App Sessions Standard" report and by looking at the "Sessions" field I am able to recreate the numbers displayed for the "Sessions" metric. However if I try to infer the active devices by looking at the "Unique Devices" field my numbers for individual days are in the same ballpark (deviations may be attributable to privacy reasons?), but the total number of devices is way off. Is there a better way to recreate this metric?
Replies
2
Boosts
2
Views
536
Activity
3w
I hooked an AI up to App Store Connect, Meta Ads, and Firebase via official APIs. It is a marketing monster, but does this violate Apple's TOS?
Today I witnessed the real power of AI beyond just writing code. I am using it as a super marketer to drive up my app business, and the results are incredible. This is what I have set up. I provided read access to the AI using their official APIs for: App Store Connect Apple Search Ads Meta Ads Firebase Analytics Local app source code By combining the source code with real performance data, the AI ran a thorough analysis and suggested concrete, actionable items to improve my overall app business. My main concern is whether this is allowed by Apple. Specifically, does Apple permit using AI agents to query App Store Connect and Apple Search Ads through their official APIs? The setup is too powerful not to use, but we still need to abide by Apple rules. Has anyone else looked into this or tried a similar workflow?
Replies
1
Boosts
0
Views
273
Activity
Oct ’26
How to specify dimensions in App Analytics reports API?
I'm fetching Apple Store Connect data from the API (in particular, fetching the App Store Purchases report) and trying to replicate the dashboards that we can see under Analytics > Metrics. The thresholding that Apple applies ("Omits values with data from fewer than 5 users or 5 unique devices") means that a lot of data is lost. Is there a way of specifying the dimensions of the report? If we had less dimensions, the threshold would affect to less rows of data, and we would be able to analyze more data. It's strange that from the website of App Store Analytics we can get the data, but through the automated reports we cannot or a lot of data is lost due to not being able to set the report dimensions.
Replies
2
Boosts
0
Views
647
Activity
Oct ’26
Request for a supported endpoint to create apps (POST /v1/apps)
We are requesting a supported App Store Connect API endpoint for creating a new app record, for example POST /v1/apps. We run an automated "create app" workflow that sets up new apps as part of our app management service. The App Store Connect API supports reading and updating apps, but the Apps documentation (https://developer.apple.com/documentation/appstoreconnectapi/apps) lists no way to create one. A new app can only be created on the App Store Connect website. Today our approach is using a third-party library (fastlane's Spaceship) that calls the private endpoints behind the App Store Connect website. Those endpoints can change at any time, and if they do, app creation and our automation will stop working. A supported endpoint, authenticated with an App Store Connect API key, would let us create apps reliably. Thank you for considering this request.
Replies
0
Boosts
1
Views
186
Activity
Oct ’26
App Store Connect API authorization for Game Center player score and achievement submissions
We are calling these App Store Connect API endpoints from our server: curl --request POST \ --url https://api.appstoreconnect.apple.com/v1/gameCenterLeaderboardEntrySubmissions \ --header 'Authorization: Bearer JWT_Token' \ --header 'Content-Type: application/json' \ --data '{ "data": { "type": "gameCenterLeaderboardEntrySubmissions", "attributes": { "bundleId": "bundleId", "score": "1", "scopedPlayerId": "scopedPlayerId, "submittedDate": "date", "preReleased": true, "vendorIdentifier": "vendorIdentifier" } } }' curl --request POST \ --url https://api.appstoreconnect.apple.com/v1/gameCenterPlayerAchievementSubmissions \ --header 'Authorization: Bearer JWT_Token' \ --header 'Content-Type: application/json' \ --data '{ "data": { "type": "gameCenterPlayerAchievementSubmissions", "attributes": { "bundleId": "bundleId", "vendorIdentifier": "vendorIdentifier", "percentageAchieved": 1, "scopedPlayerId": "scopedPlayerId, "submittedDate": "Date", "preReleased": true } } }' According to https://developer.apple.com/documentation/appstoreconnectapi/app-store-connect-api-3-2-release-notes We should be able to set player score and achievements. We use an active Team App Store Connect API key and generate an unscoped ES256 JWT with aud: appstoreconnect-v1. The key has high-level App Store Connect permissions. We followed documentation: https://developer.apple.com/documentation/appstoreconnectapi https://developer.apple.com/documentation/appstoreconnectapi/post-v1-gamecenterplayerachievementsubmissions https://developer.apple.com/documentation/appstoreconnectapi/post-v1-gamecenterleaderboardentrysubmissions Both requests return: { "status": "403", "code": "FORBIDDEN_ERROR", "title": "This request is forbidden for security reasons", "detail": "The API key in use does not allow this request" } The player is authorised via GameKit on the mobile app. The API key can read: https://api.appstoreconnect.apple.com/v1/apps/:id https://api.appstoreconnect.apple.com/v2/gameCenterLeaderboards/:id. Which exact App Store Connect API key role or permission is required for these endpoints? Is server-to-server submission supported using a Team API key?
Replies
0
Boosts
0
Views
195
Activity
Oct ’26
App Store Connect Metrics via REST API
I hope this message finds you well. I’m reaching out to ask whether specific App Store Connect metrics available in the App Analytics dashboard can also be accessed via the App Store Connect REST API. I have reviewed the official API documentation, but I couldn’t find confirmation regarding the metrics listed below. Could you kindly clarify if the following metrics are available through the REST API? And if so, could you point me to the relevant endpoints or documentation? From the "Usage" group: Installations (Opt-in only) Active Devices Deletions (Uninstalls) From the "App Store" group: Impressions (Unique Devices) Product Page Views (Unique Devices) If these metrics are not available via the REST API, is there an alternative method to programmatically access or export them? Thank you very much in advance for your help and guidance.
Replies
5
Boosts
3
Views
1.8k
Activity
Oct ’26
Unable to download App Store Connect API keys in iOS Safari
Posting here to see if anyone has found a workaround and/or to get Apple employees' eyes on it. I'm not sure when this bug was introduced but I've found that in Safari on iOS 27, I'm unable to download API keys from App Store Connect. Reported as a Safari bug in Feedback Assistant (FB24994724). I checked web inspector's console and network logs for both my iPad and iPhone; no JS errors and a nondescript network error for the key's fetch request. Google Chrome for iPad/iPhone downloads the .p8 key file without issue, so this feels more like a Safari bug than an App Store Connect bug.
Replies
0
Boosts
0
Views
356
Activity
Sep ’26