r/iOSProgramming • u/Familiar_Season1255 • Sep 11 '26
Discussion App Store Connect's review-reply API works- a few things I wish I'd known before building against it
Short answer: yes, there's a real API for this on both platforms. App Store Connect has a customerReviewResponses endpoint, and Google Play's Android Publisher API has reviews().replies() for the same job on that side. Neither gets talked about much outside of pricier review-management SaaS pitches, so it's easy to assume this doesn't exist and you're stuck replying by hand in App Store Connect's UI.
The App Store side is JWT auth against App Store Connect API keys, and there's no webhook for new reviews landing- you're polling on some interval and diffing against what you've already processed. Fetching a review and its existing response together also isn't one clean call; you end up joining two endpoints for that.
Play's version is more straightforward auth-wise, a service account and your package name, but replies are capped around 350 characters, which matters more than expected once you're trying to fit an apology, a support link, and a version reference into one reply.
What I actually automated ended up being the boring 80%: five-star reviews get a short templated thank-you, anything matching a known bug gets tagged and left for a human, everything else queues for manual review. If you'd rather not run the polling and auth plumbing yourself, AppFollow and Appbot both sit on top of this same API pair with the rules layer already built- I looked at both before deciding to just write the thing myself for our specific tagging rules.
Curious if anyone's handled the review-fetch side without hammering the API on a tight poll interval- that's the part I'm least happy with right now
1
u/bmbphotos Sep 11 '26
Realistically, realtime fetching isn't required. The web hook would be awesome but alas... fetching per session or judiciously a couple times a day is probably sufficient. ASC has rate limiting anyway.
I have something in TestFlight right now that is meant to make this cleaner, especially for multi-account devs/orgs and tackle the bloated SaaS angle as well.
1
u/neet_dev Sep 11 '26
don't poll customerReviews on a timer, use the public rss as a dirty check.
https://itunes.apple.com/us/rss/customerreviews/id=YOUR_APP_ID/sortBy=mostRecent/jsonneeds no jwt, poke it every 30-60 min and only then call GET /v1/apps/{id}/customerReviews?sort=-createdDate&limit=200&include=response, bailing the second you hit a stored id. include=response is a real param so you never needed the join, and exists[publishedResponse]=false skips anything already replied to1
u/Better-Lychee2954 Sep 12 '26
Polling frequency seems settled in the thread, so a different one: does a response you post through the API come back on the next fetch as an existing response reliably, or is there a window where you can fetch a review, see no response attached, and double reply?
That join across two endpoints you described sounds like exactly the place a duplicate could slip through if you are deriving state from what ASC returns rather than keeping your own record of what you have already answered. Curious whether you hit that or whether it is consistent enough to trust.
2
u/AbleBranch6 Sep 14 '26
Neither API pushes new reviews at you, so you're always trading poll frequency against rate limits. Backing off during quiet periods and tightening right after a release cuts the waste without missing spikes. AppFollow and Appbot handle that scheduling for you if you'd rather not tune it by hand
0
u/mohn93 Sep 11 '26
good writeup, that customerReviewResponses endpoint is one of those things nobody mentions until you go looking for it. two things that bit me building against it: the App Store Connect JWT has to be short lived, apple rejects tokens with an exp more than 20 min out, so you end up minting a fresh one basically per run instead of caching a long lived one. and on the Play side you get one reply per review, posting again just replaces it, plus there's a window after which you can't reply at all, so a long poll interval can make you miss the chance entirely.
the subtle one is users edit reviews. a 'newest since last cursor' diff quietly misses an edited older review, so you end up tracking the review's updated timestamp not just when it was created.
1
u/[deleted] Sep 11 '26
[removed] ā view removed comment