Extension discovery
Use Chrome Web Store endpoints to turn extension discovery into repeatable API requests with documented inputs and JSON responses.
Collect Chrome Web Store extension discovery, listing, review, permission, and privacy signals as normalized JSON for app intelligence and browser-extension research workflows.
Extract public Chrome Web Store extension metadata, search results, reviews, permissions, privacy details, categories, and charts as JSON.
Endpoint families
6
Documented params
53
Examples
12
Live catalog snapshot
Active endpoints
12
Methods
GET
Required params
22
Schema refs
12
{
"platform": "Chrome Web Store",
"endpoint": "chromewebstore-search",
"method": "GET",
"path": "/chromewebstore/search",
"auth": "apiKey"
}Use cases
Extract public Chrome Web Store extension metadata, search results, reviews, permissions, privacy details, categories, and charts as JSON.
Use Chrome Web Store endpoints to turn extension discovery into repeatable API requests with documented inputs and JSON responses.
Use Chrome Web Store endpoints to turn review monitoring into repeatable API requests with documented inputs and JSON responses.
Use Chrome Web Store endpoints to turn permission and privacy analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/chromewebstore/categories
/chromewebstore/category
/chromewebstore/charts
/chromewebstore/collection
/chromewebstore/developer
/chromewebstore/item
Endpoint catalog
/chromewebstore/searchReturns Chrome Web Store search result cards for a keyword, each with id, name, rating, user count, publisher and detail URL. Defaults: `num=30`, `country=us`, `lang=en`.
/chromewebstore/itemReturns normalized detail for a Chrome Web Store extension or theme, including name, rating, rating count, user count, version, last-updated date, size, supported languages, developer, category, screenshots, and privacy links. Defaults: `country=us`, `lang=en`.
/chromewebstore/reviewsReturns the reviews the store renders on an item's reviews page, each with author, star rating, text, posted/edited dates and reviewed version. Defaults: `num=20`, `country=us`, `lang=en`.
/chromewebstore/permissionsReturns the permissions a Chrome Web Store extension declares in its manifest: `permissions`, `optional_permissions`, `host_permissions`, `optional_host_permissions`, plus `manifest_version` and `min_browser_version`. Useful for security and supply-chain review. Defaults: `country=us`, `lang=en`.
/chromewebstore/privacyReturns an extension's privacy disclosures as the store renders them: the developer's data-use statement, whether it collects data, the standard data-handling declarations, and the privacy-policy link. Defaults: `country=us`, `lang=en`.
/chromewebstore/similarReturns the related-items shelf the store renders on an item's detail page. Defaults: `country=us`, `lang=en`.
/chromewebstore/suggestReturns item-name suggestions for a search prefix, drawn from the top store-search results. Defaults: `num=8`, `country=us`, `lang=en`.
/chromewebstore/chartsReturns the item cards in a store top chart. `chart` accepts `trending`, `popular`, or `notable`. Defaults: `chart=popular`, `num=50`, `country=us`, `lang=en`.
/chromewebstore/categoriesReturns the reference taxonomy for the list endpoints: extension category groups and their subcategory slugs, the top-chart identifiers, and known curated collection slugs.
/chromewebstore/categoryReturns the item cards listed under an extensions category slug (e.g. `productivity/tools`, `lifestyle/shopping`, `make_chrome_yours/privacy`). Use /chromewebstore/categories for the reference taxonomy. Defaults: `num=50`, `country=us`, `lang=en`.
/chromewebstore/collectionReturns the item cards in a curated store collection slug (e.g. `editors_picks_extensions`, `dark_mode`, `ai_productivity`). Use /chromewebstore/categories for known collection slugs. Defaults: `num=50`, `country=us`, `lang=en`.
/chromewebstore/developerReturns a Chrome Web Store publisher (developer) by publisher id, including the disclosed trader details — legal name, email, phone, address, website, and D-U-N-S number — plus the publisher's listed items ("More from ..."). Trader fields are only present for publishers that identify as EU traders. Defaults: `num=50`, `country=us`, `lang=en`.
Related APIs
App Stores
Run App Store search queries and turn App Store listings, rankings, reviews, and developer pages into structured JSON for app intelligence, ASO research, and competitor monitoring workflows.
App Stores
Build Android app intelligence workflows with structured Google Play data.