There is some form of limited Web Store app/ext stats API available.
It is used by the My Extensions (
https://chrome.google.com/webstore/
detail/igejgfmbjjjjplnnlgnbejpkpdajkblm) extension, along with Web
Store screen scrapes, to provide extension stats. It does a pretty
good job and I recommend it for stats tracking.
Anyway, these APIs are also used by the Web Store to display some of
the data on app/ext pages via XHR. There doesn't seem to be any
documentation on these anywhere, so everything I know about them I've
gleaned from an inspection of these pages. If any Google staff reading
this can point us to an official reference for these APIs, it would be
much appreciated.
Anyway, if you check out the XHR calls made by any extension page via
Chrome Dev Tools, you'll find these two:
For extension comments:
https://chrome.google.com/reviews/json/search
For star ratings breakdown:
https://chrome.google.com/reviews/json/lookup
You can play around with the request payload parms to "discover"
different behaviors of these APIs by submitting via Fiddler or similar
tool. Some parms are pretty self-explanatory. For example, you may
notice that the "search" call now has a "sortBy":"quality" parm that,
if omitted, will yield comments in the original desc date order that
we all know and love. Using Fiddler, I was also able to bulk-download
the JSON for all comments to-date submitted for my extension, in desc
date order (if you try this, make sure you fetch them in increments of
100).
Given all the outcry, it would be simple (and wise) for Google to just
remove the "sortBy":"quality" parm to revert comment sorting to the
date desc sort in the interim while this all gets sorted out... that's
just my 2c editorial to add a little fuel to the fire :)
Cheers,
Hans