TestingOps.ai

App markets · Native connection

Apple App Store and TestingOps: review insights for iOS testing

App Store reviews show where iPhone and iPad users run into trouble. TestingOps collects them with an App Store Connect API key or from Apple's public reviews feed and turns them into insights and test ideas in the knowledge base.

  • Native connection
  • Available with limits
Request a demo App Store Connect API: customer reviews
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

Apple App Store and TestingOps in short

The App Store connection works in two modes: with an App Store Connect API team key it reads reviews of the last 90 days with rating, title, text, date and territory, and without a key it reads the most recent reviews from Apple's public feed for the countries you choose, which include the app version.

TestingOps writes rating trends and breakdowns and, with an AI model, themes with test ideas to the project's knowledge base. Version breakdowns and regression candidates need the app version, so they come only from the public feed.

Nothing is written to App Store Connect and no responses are posted; the analysis points to what to test, it does not test the app.

What it does

What it does for your testing

  1. 1

    Ninety days of reviews with an API key

    Input
    Reviews from the App Store Connect API: rating, title, body, date and territory
    TestingOps
    Pages newest first, up to 15 pages of 200 per sync, and stops at a review it already has
    Output
    Rating distribution, the 30-day trend and a breakdown by territory
  2. 2

    Version signals from the public feed

    Input
    Recent reviews from Apple's public feed with their app version
    TestingOps
    Breaks reviews down by version (at least 3 reviews) and compares each version with the previous one
    Output
    Regression candidates for a release
  3. 3

    Themes become iOS test ideas

    Input
    Review titles and texts
    TestingOps
    With an AI model, sorts reviews into themes such as payments or performance and writes 2 to 4 test ideas per theme with quotes from stored reviews
    Output
    Theme sections agents use when they plan iOS test cases

Step by step

How it works

  1. Choose a modeUse an App Store Connect API team key (Issuer ID, Key ID and the .p8 private key) for 90 days of reviews, or leave all three empty to read Apple's public feed.
  2. ConnectUnder Integrations → App markets → App stores → App Store, enter the key fields, or only the countries for the public feed (default tr, us). Issuer ID, Key ID and key must be all set or all empty.
  3. Link an appIn the project's Knowledge tab, add a source under App reviews and paste the App Store link (apps.apple.com/…/id1234567890) or the numeric app ID.
  4. Reviews are kept and maskedEach sync stores new and changed reviews, with e-mail addresses and phone-like numbers masked. Reviewer nicknames are never requested.
  5. Insights are writtenThe statistics are rewritten on each sync; the AI step runs only for reviews it has not seen.

Connect

Setup

  1. API key mode: in App Store Connect, create a team API key with the Admin or Customer Support role and note the Issuer ID, the Key ID and the .p8 file.
  2. In TestingOps, open Integrations → App markets → App stores → App Store and enter the Issuer ID, the Key ID and the .p8 file contents, or leave them empty and enter the countries for the public feed. Select Test connection, then Save.
  3. In the project's Knowledge tab, select Add source under App reviews and paste the App Store link or the numeric app ID.
  4. Select Sync now. Automatic syncs follow, and the AI step runs when new reviews arrive.

Documentation: App Store Connect API: customer reviews · Creating App Store Connect API keys

Where you connect it in TestingOps: Integrations → App markets → Apple App Store

Use cases

Use cases

Watch a market after a launch

Trigger
The app launches in a new country
Uses
Reviews by territory and the 30-day trend
Agent activity
Compares the new market's ratings and themes with the others when it plans tests
Result
Localisation and market-specific test ideas
Condition
In feed mode, the country must be in the connection's country list

Spot a weak iOS release

Trigger
A new version is out and ratings drop
Uses
The version breakdown and regression candidates from the public feed
Agent activity
Reads the Versions and regressions section before it plans regression tests
Result
Tests focused on the version that got worse
Condition
Needs feed mode: the API key mode gives no app version

Turn purchase complaints into test ideas

Trigger
Reviews mention failed purchases or subscriptions
Uses
The payment theme's summary, test ideas and quotes
Agent activity
Writes test cases from the ideas after checking the existing cases
Result
Draft cases for the purchase flow, ready for review
Condition
Draft cases straight from bug reviews are available only through the TestingOps API

Capabilities

Capabilities and limits

What is read

  • API key mode: rating, title, body, created date and territory per review, newest first, up to 15 pages of 200 per sync; no app version, device, OS or language
  • Feed mode: rating, title, content, app version, updated time and country from Apple's public feed of each chosen country, up to 10 pages per country; recent reviews only
  • Not read: reviewer nicknames and IDs, and responses to reviews

What is produced

  • Overview: rating distribution and average, the last 30 days against the 30 before, and breakdowns by territory and, in feed mode, by app version
  • Versions and regressions: regression candidates when app versions are known, which means feed mode
  • With an AI model: theme sections with summaries, test ideas and quotes from stored reviews

Where it can write

  • Nothing in App Store Connect or on the App Store; no responses to reviews
  • In TestingOps: masked reviews, kept for 90 days and up to 2,000 per link, and the insight sections in the project's knowledge base

How it connects

  • App Store Connect API with a team key: TestingOps signs a short-lived token (20 minutes) with your .p8 key
  • Or no credentials: Apple's public customer reviews feed per country, which Apple does not document

Account and permissions

  • API key mode: an App Store Connect API team key (Issuer ID, Key ID and .p8 file) with the Admin or Customer Support role
  • Feed mode: no account, only the countries to read (default tr, us)

Limits

  • API key mode gives no app version, device, OS or language, so version breakdowns and regression candidates need feed mode
  • Feed mode returns only recent reviews, and Apple does not document the feed
  • Feed mode has nothing to check on Test connection; API key mode lists the key's apps
  • The AI step sorts up to 300 new reviews per sync in batches of 100 and runs at most every 12 hours on automatic syncs (Sync now does not wait); it uses the project's AI model and your AI allowance, and without them only the statistics are written
  • Masking is pattern based: e-mail addresses and phone-like numbers are masked before storage, in what the AI step sees and in its output, but names or addresses typed into a review can remain
  • Review analysis does not test the app: test cases written from it run separately on an execution provider

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team links its iOS fitness app in feed mode for the US and Germany. Two weeks after version 3.8, the Versions and regressions section shows a higher 1–2 star share for 3.8 than for 3.7, and the performance theme collects reviews about workouts that stop syncing.

An agent reads the theme's test ideas and plans cases for syncing a workout after the app returns from the background, and the team runs them on an iPhone before the next release.

Frequently asked questions

API key or public feed: which should we use?

An App Store Connect API key gives up to 90 days of reviews with their territory, but no app version. The public feed needs no key and includes the app version, but only recent reviews. Version breakdowns and regression candidates need the version, so they come only from the feed.

Which App Store Connect role does the key need?

A team key with the Admin or Customer Support role. TestingOps signs a short-lived token with the .p8 key on each sync; the private key itself is not sent.

Does TestingOps respond to reviews?

No. It only reads reviews. Nothing is written to App Store Connect.

Which countries are read?

With an API key, reviews from all territories, each tagged with its territory. With the public feed, the countries you list on the connection, tr and us by default.

Can it write test cases from reviews?

Theme sections contain test ideas that agents use when they write cases. Draft test cases straight from bug reviews are available only through the TestingOps API; they are tagged as iOS cases and saved as unverified drafts.

Is this iOS testing?

No. Review analysis shows where to look. Test cases for the app are written separately and run on an execution provider.

Next step

See what App Store reviews say about your latest version: request a demo and bring your app's App Store link.

Request a demoMore app markets integrations