Chrome Web Store extensions, reviews and developers as JSON
- endpoints
- 12
- credits per call
- 0–1
This API reads chromewebstore.google.com logged out and returns what the store publishes as plain JSON.
| name | rating | type | summary |
|---|---|---|---|
| AdBlock — block ads across the web | 3.91 | extension | Block ads on YouTube an… |
| Adblock Plus - free ad blocker | 3.89 | extension | Remove ads on YouTube a… |
| Ad Blocker: Stands AdBlocker | 4.79 | extension | — |
1 credit per call≈ $1/1,000 calls1,000 free credits, no card
Get a free API keyRun the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
Chrome Web Store API
5 of 12 endpoints, ready to run
Full listing with users, rating and developer
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What Chrome Web Store endpoints does ReefAPI ship?
12 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
search
1 crSearch the Chrome Web Store with the store's own filters.
- required
- —
- optional
- —
details
1 crEverything the store publishes about one extension or theme.
- required
- —
- optional
- —
reviews
1 crAn item's user reviews with star rating, text, author, dates, helpful votes, the reviewed ver…
- required
- —
- optional
- —
support
1 crThe item's public support tab.
- required
- —
- optional
- —
publisher
1 crA publisher's profile.
- required
- —
- optional
- —
categories
1 crThe store's category list for extensions and themes, with ids, slugs, labels and groups.
- required
- —
- optional
- —
category
1 crAll items of one category, in the store's order, highest rated first, trending first or most…
- required
- —
- optional
- —
top_charts
1 crThe store's top charts.
- required
- —
- optional
- —
collections
0 crThe store's curated collections (slug, title, subtitle) from its own catalogue, each with the…
- required
- —
- optional
- —
collection
1 crEvery item of one curated collection, in the store's order, with the collection's title and s…
- required
- —
- optional
- —
discover
1 crThe shelves of the store's landing pages as they are today.
- required
- —
- optional
- —
package
1 crThe item's installer package as Chrome's own update check reports it.
- required
- —
- optional
- —
Every parameter, every allowed value →
Missing a Chrome Web Store endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Chrome Web Store API works
Chrome Web Store is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 694 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From a keyword to the extensions, their users and their developers
Find the extensions for a niche, read each listing, then read what users say and who builds them.
The store's results with users, rating and badges, plus the match count.
Version, Updated date, permissions, manifest, privacy declarations and the developer's contact block.
The most critical reviews first, with the developer's replies; next_cursor for more.
The publisher's e-mail, phone, address and every item it publishes.
A list of extensions in a niche with users, ratings, permissions, developer contacts and the complaints users post.
curl -X POST https://api.reefapi.com/chrome-web-store/v1/details \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"id":"eimadpbcbfnmbkopoojfekhnkhdbieeh"}'{
"ok": true,
"data": { … },
"meta": {
"api": "chrome-web-store",
"endpoint": "details",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Chrome Web Store field actually contains
Fields that read differently from how they look. Every row was measured against live Chrome Web Store pages on 2026-11-16.
| Field | What it holds |
|---|---|
| users | The store's own user count, the number the listing prints as "7,000,000 users". Matched the page on 28 of 28 listing pages (25 different items). |
| rating and rating_count | The exact average (4.291) and the exact count (13293). The page rounds both: "4.3" and "13.3K ratings". Both matched the page's rounded figures on 28 of 28 listing pages. |
| updated and updated_at | The listing's "Updated" timestamp. updated_at is exact (UTC); updated is its UTC date. The page prints the date in the visitor's own time zone, so it can read one day earlier or later (4 of 28 listing pages, each one the visitor's local date). |
| developer | The listing's developer block, exactly as published: name, legal name, publisher name, e-mail, phone, postal address, website, D-U-N-S and trader status. The first line of the page's Developer block is publisher_name (27 of 27). Phone, address and D-U-N-S exist only when the developer published them: 5 of 12 productivity items had a phone, 0 of 8 themes. |
| is_established_publisher | The page's "The publisher has a good record with no history of violations" badge (26 of 26 non-Google listing pages). On Google's own items the page shows "This extension was developed by Google" instead; is_by_google says so. |
| is_featured | The "Featured" badge, shown with "Follows recommended practices for Chrome extensions" (28 of 28 listing pages). |
| privacy.data_collected | The data types the developer declares the item handles, in the page's own wording (Personally identifiable information, Location, Web history …). Empty when the page says the developer will not collect or use your data (28 of 28 listing pages). |
| size | The page's own size text ("839KiB"); size_bytes converts it. `package` returns the installer's exact size in bytes. |
| total | Search: the store's match count, an estimate that can move by a few between pages; paging reached 367 of 372 for 'ad blocker' and 257 of 298 for 'vpn'. Category lists have no count. |
A removed item, or one not offered in the chosen country, returns NOT_FOUND and names the replacements the store suggests. Reviews and support issues of an item that does not exist return NOT_FOUND, not an empty list.
Chrome Web Store coverage, measured
Every number below was read from the live Chrome Web Store on 2026-11-16.
Compared with the store's own listing pages (28 pages, 25 different extensions and themes): 534 of 553 values matched. Users, rating, rating count, version, size, languages, Featured badge, trader status, e-mail, phone and D-U-N-S matched on every page; the differences were the Updated date shown in the visitor's time zone (4), Google's own item showing "developed by Google" instead of the established-publisher line (2), and one listing the visitor's country does not offer (13).
Up to 500 reviews per page, every review reachable with a cursor (Dark Reader: 8,178). Support tab: problems, questions and suggestions, up to 500 per page (Dark Reader: 1,355 issues).
Search up to 100 results per page; categories up to 200 per page (Developer Tools: 1,200 different items in 6 pages); 30 categories; top charts Trending, Popular, New and notable (25 each); 99 curated collections.
Name, legal name, e-mail, phone, address, website, D-U-N-S and trader status as the listing publishes them; phone, address and D-U-N-S only for developers who published them.
US store by default; the German store with country=de. Items offered in one country only are missing from the other's search and details.
Search counts are the store's estimate: paging reached 367 of 372 results for 'ad blocker' and 257 of 298 for 'vpn'. Category lists carry no count. Nothing behind a Google login.
What people build with Chrome Web Store
The jobs this data is most often used for.
Track users, ratings and versions of competing extensions over time.
Build lead lists of extension developers with their published e-mail, phone and address.
Audit extensions' permissions, host permissions and declared data collection for security reviews.
Mine reviews and support issues for bugs, feature requests and sentiment.
endpoints
credits per call
What Chrome Web Store data costs
The cheapest call here is 0 credits, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 694 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/chrome-web-store/v1/details \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"id":"eimadpbcbfnmbkopoojfekhnkhdbieeh"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/chrome-web-store/v1/details",
headers={"x-api-key": REEF_KEY},
json={
"id": "eimadpbcbfnmbkopoojfekhnkhdbieeh"
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Chrome Web Store.
Do I need a Google account?▾
No. Everything is read logged out from the public store.
Which data does a listing return?▾
Users, average rating and rating count, version, Updated date, size, languages, category, badges, in-app purchases, permissions and host permissions, the full manifest, description, screenshots and video, support link, privacy policy, the data types the developer declares, the developer's contact block and the store's related items.
Does it return developer e-mails and phone numbers?▾
Yes, exactly as the listing publishes them. On 2026-11-16, 34 of 36 sampled listings carried an e-mail; phone, address and D-U-N-S appeared on the listings of developers who declared themselves traders (5 of 12 productivity items had a phone). `publisher` returns the same block plus every item of that publisher.
How many reviews can I get?▾
All of them, up to 500 per page with a cursor. Dark Reader: 8,178 reviews in all languages; four consecutive pages of 200 returned 800 different reviews. Sort by recent, helpful, lowest or highest rating, filter by star rating (1-5) and by review language.
Which search filters work?▾
The store's own: extensions or themes, minimum rating (2, 3, 4 or 5 stars), Featured and Established publisher. On 'vpn' the store counts 298 results, 183 from established publishers, 55 Featured. The store's rating filter lets some lower-rated items through; this API removes them, so every row meets the minimum.
Can I list a whole category?▾
Yes, 200 items per page with a cursor, sorted by relevance, highest rated, trending or recently updated, optionally Featured or Established publishers only. Developer Tools: 6 pages of 200 returned 1,200 different items.
Is the catalogue the same in every country?▾
No. Some items are offered only in some countries. `country` chooses the store (us by default, or de): Capital One Shopping opens in the US store and is NOT_FOUND in the German one.
What is not available?▾
Anything behind a Google login (installing, rating, your own items) and the developer dashboard. The store publishes no result count for category lists.
What is the Chrome Web Store API?▾
Chrome Web Store API is a ReefAPI endpoint group for chrome web store extensions and themes: search with the store's filters, full listings with users, rating, version, permissions and developer contact details, reviews, support issues, publishers, categories, top charts and collections. It returns live JSON through POST requests under /chrome-web-store/v1.
Is the Chrome Web Store API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Chrome Web Store calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Chrome Web Store login or account?▾
No login to Chrome Web Store is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Chrome Web Store data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Chrome Web Store API use?▾
Chrome Web Store actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Chrome Web Store from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call chrome-web-store actions with the same key, credit pool and JSON envelope used by normal REST requests.
13 Developer Tools APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Chrome Web Store, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 693 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-16.