Skip to content

Google Play Scraper API

A managed endpoint for turning a Google Play app listing into a structured record you can store, compare and chart.

OUTPUT FORMATSHTMLJSONMarkdown

You supply an app identifier; the service loads the store page, handles its interactive elements, and returns the fields you define as JSON.

What a Google Play app record can contain

A single request can return the app name, star rating, review count, download range, content rating, support contact, last-updated date, category tags, release notes, developer name, Android OS requirement, in-app purchase range and original release date. The response is JSON, so it can feed a dashboard, a spreadsheet import or a comparison job without a separate parsing step.

Those fields support three common jobs: watching how an app's rating and review volume move over time, mapping a developer's catalogue and pricing posture, and comparing how the same listing appears in different storefronts. Download figures arrive as ranges rather than exact counts, and in-app prices arrive as a range per item, so treat both as bands when you build charts or alerts.

The request shape: one identifier, several controls

The documented input is app_id, the unique Google Play identifier for the app (for example, a package-style value). The example request also sets custom_google, wait_browser, premium_proxy, extract_rules, js_scenario and country_code, and applies retries. Each control has a job:

  • app_id selects the listing.
  • country_code selects the regional storefront, so the same app can be compared across markets.
  • extract_rules maps output keys to CSS selectors, which is how the response is shaped into named fields.
  • js_scenario performs browser actions before extraction, such as clicking a control and waiting, which matters when part of the page is revealed only after interaction.
  • wait_browser and premium_proxy govern how the page is loaded and routed.

The exact request and response contracts are supplied as protected modules and should be used as-is rather than retyped.

Field map: which value answers which question

Use this map when deciding which keys to keep in your own schema.

  • Name and developer (name, offered_by): identity and portfolio grouping.
  • Rating and reviews (rating, reviews): reception and engagement trend.
  • Downloads (downloads): adoption band, not an exact install count.
  • Content rating (content_rating): audience suitability.
  • Support contact (support_email): publisher contact for follow-up.
  • Update and release dates (updated_on, released_on): maintenance cadence and age.
  • Tags (tags): category and genre classification.
  • What's new (whats_new): recent change notes; can be empty.
  • OS requirement (android_os_requirement): device compatibility floor.
  • In-app purchase range (in_app_purchase_range): monetization band per item.

A field that is empty in one snapshot is not necessarily an error; release notes, for instance, may legitimately be blank.

Reading a captured snapshot

The supplied example output for a board-game app shows how the fields combine into a usable profile: a 4.2-star rating with a review count in the millions, a download band of 1B+, an in-app purchase range spanning roughly half a dollar to several hundred dollars per item, an Android requirement of 7.0 and up, and a release date in December 2016. Read together, those values describe a mature, high-volume title with a wide monetization spread. The example's support email belongs to the app's own developer, not to the API provider, so treat it as a field value rather than a contact route for the service.

Treat any such snapshot as a point-in-time capture, not a live figure. Ratings, review counts and prices change, and the example's date labels belong to the capture, not to your run. The exact output contract is supplied as a protected module.

Choosing an extraction method

Three routes exist for getting data out of a Google Play page, and they suit different levels of maintenance:

  1. Selector-based extraction (extract_rules): you name the CSS selectors for each field. Precise and cheap per call, but selectors can break when the page markup changes.
  2. AI extraction: you describe the fields in plain language and the model adapts to layout changes. Less selector upkeep, useful when you need many fields or the page shifts often.
  3. Search-based discovery: pull Google Play results from search listings when you need to find apps rather than read one known listing.

A practical default is selector-based extraction for a fixed, small field set you monitor on a schedule, and AI extraction when the field list is broad or the layout is unstable.

Reliability and how failures differ

The service handles Google Play's interactive elements, including controls that reveal more content, and uses proxy management, browser fingerprinting and JavaScript handling to keep extraction complete. That reduces the usual causes of partial records.

Failures are not all the same, and the fix differs:

  • Invalid or missing API key: the response begins with an invalid-key message; the remedy is to supply a valid key.
  • Blocked or incomplete page: fields come back empty or missing even though the request succeeded; the remedy is to adjust loading, proxy or interaction settings.
  • Credit exhaustion: requests stop succeeding once the plan's credits are used; the remedy is to raise the plan or reduce call volume.

Separating these cases early saves debugging time.

Regional tracking

Because country_code selects the storefront, the same app can be read as it appears in different markets. That lets you compare presentation, price and ranking position across regions. Keep the country code with every stored record so comparisons stay valid; a price band from one market should not be charted against another without that label.

Capacity and credits

How many apps you can monitor depends on your plan. Each call consumes credits according to the complexity of the request, so a heavier request (more browser interaction, premium routing) costs more than a light one. Plan for the number of apps multiplied by the polling frequency, then add headroom for retries. The published plan tiers and their credit and concurrency figures are supplied as a separate factual table module and should be read from there rather than restated here.

Published plan tiers (captured reference)
PlanMonthly priceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

Reference figures for the published tiers; prices exclude VAT and are subject to change. Check current pricing before relying on any figure. All tiers include geotargeting, screenshots and extraction rules, and dedicated scraping APIs. Support and account-manager commitments shown here are first-party service terms and require owner confirmation before publication.

Frequently asked questions

What data can I extract from Google Play?

App name, rating, review count, download range, content rating, support contact, update history, category tags, update notes, developer information, OS requirements, in-app purchase ranges and release dates, delivered as JSON.

How reliable is the Google Play scraper?

It is built to handle Google Play's content structure, including interactive elements that reveal more content, using proxy management, browser fingerprinting and JavaScript handling so extraction stays complete.

Is there an AI Google Play scraper API?

Yes. You describe the fields you want in plain language, and the AI extraction adapts to layout changes and returns clean JSON, working alongside the anti-bot handling.

Can I track apps across different countries?

Yes. Supply a country code to read the regional version of Google Play, which lets you compare presentation, pricing and ranking across markets.

How do I get started with the Google Play API?

Sign up for an API key, install the client, supply the app IDs you want to track, and start collecting data. Ready-to-use code examples are available in the documentation. Any trial credits or signup terms are set by the account owner and should be confirmed at signup.

Is there a limit to how many apps I can monitor?

Capacity follows your plan. Each call uses credits based on request complexity, and plans scale from a handful of competitors to broad market analysis.

Is the example output live data?

No. The example is a captured snapshot for illustration. Ratings, review counts and prices change, so treat any stored record as a point-in-time capture and re-request when you need current values.

Why would a field come back empty?

Some fields are legitimately blank, such as release notes when none are shown. Others can be empty if the page did not fully load or an interactive element was not triggered. Check the loading and interaction settings before assuming the data is missing.