Chapter 1. What a Play Store API is, and what it is not

The difference between Google's own developer API and a listing data API, and why the second one exists.

Search for "Play Store API" and you will meet two very different things under the same name.

Google's Play Developer API

Google publishes the Google Play Developer API for the owners of apps. With a service account linked to your Play Console you can upload builds, edit your listing, read and reply to reviews and verify purchases. It never returns data about apps you do not own, and it has no search.

A listing data API

The other kind treats the Play Store as a public catalogue. It reads public listings (anyone can open them in a browser) and serves them as JSON: one app by package name, or many apps by genre, installs, rating or date. That is what market research, app directories, ASO tools and analysts need, and that is what this handbook is about.

What a listing record contains

• Identity: package name, title, publisher, genre.
• Popularity: install band and an estimate, rating, number of ratings and reviews.
• Commerce: price, in-app purchases, ads.
• Lifecycle: release date, last update, current version, required Android version.
• Media: icon, screenshots, video.

What it does not contain

No APK files, no private sales figures, no review texts. Install counts are Google's public bands plus an estimate, not Play Console numbers. Charts are snapshots, not a live feed.

The first request

curl -H "X-API-Key: $API_KEY" \
  "https://playapi.info/api/v1/app?id=com.duolingo"

The next chapter repeats this in Python and adds search and pagination.