Skip to the content

App Store Connect

The App Store Connect key is what turns an App Store listing into something an agent can argue about: the downloads behind a keyword, the reviews nobody answered, the release notes that still describe last quarter.

What Kwern reads

Analytics, day by day

Impressions, product page views and downloads, day by day, from Apple's own analytics reports.

The listing metadata

The listing metadata an agent argues with: keywords, description and release notes.

Customer reviews, live

Customer reviews, read live at the moment an agent looks at them.

Kept day by day

impressions, page views, downloads. Every day ever seen is kept and never windowed, so a range you ask for a year from now still answers.

What Kwern can change, once you approve

A review reply

A reply to a customer review, posted from your developer account.

The promotional text

The promotional text of the live version.

How the connection is made

Connecting the account

You paste an App Store Connect team API key — issuer id, key id and the whole .p8 file. Kwern proves the key signs a token Apple accepts, then stores it encrypted.

Binding it to a product

Nothing. App Store Connect reads the app of the product's App Store surface, so there is no app to pick.

What Kwern never does

Never a version, a price or a build

Kwern never submits a version, never changes a price, and never touches a build.

The key's role is Apple's

The key's role is Apple's decision. A key with read-only rights is refused on a write and keeps reading; the connection stays healthy.

Reviews are not snapshotted

Reviews and listing metadata are read live when an agent asks for them. They are not kept in the daily snapshot.

Questions

Someone is asking for what you built today.

On Reddit, on X, in ChatGPT's answers. Kwern finds them every morning and drafts the reply in your voice; you decide what goes out.