Browser Extensions Scraper: Chrome Web Store, Firefox Add-ons & Edge Add-ons

One actor, three stores, one row shape. Give it extension URLs or ids from the Chrome Web Store, Firefox Add-ons (AMO) or Edge Add-ons, a Firefox / Edge search, or Chrome / Firefox categories, and get back users, rating, version, last update, permissions, developer, category, languages and screenshots for every extension. Public store pages and APIs only: no login, no proxy, no browser.

What you can ask for

Input	Chrome Web Store	Firefox Add-ons	Edge Add-ons
Extension URL or id	✔ full page	✔ full record	✔ store API
Search by keyword	— (the store has no public search listing; its /search pages are closed to robots)	✔ up to thousands, 8 sort orders	✔ all results, by relevance, rating or popularity
Category	✔ the store's top ~32 per category, optionally every page opened	✔ full listing, most users first	—
Editorial collection	✔ /collection/... pages (Favorites of 2025, Works with Gmail, …), 10-20 picks each	—	—

Chrome and Edge share the 32-letter id format; set Store for bare ids to say which store a bare id belongs to (URLs are always recognised by their domain).

Output

Every row has the same keys whatever the store: store, id, url, name, summary, description, rating, ratingCount, users, version, updatedAt, createdAt, size, developerName, developerEmail, developerWebsite, supportUrl, privacyPolicyUrl, category, categories, languages, permissions, hostPermissions, optionalPermissions, manifestVersion, minBrowserVersion, icon, screenshots, isFeatured, license, downloadUrl, relatedIds, query, position.

Chrome rows read from their page add the publisher's trader details where the store shows them: developerLegalName, developerCompany, developerAddress, developerPhone. Firefox rows add guid, slug, weeklyDownloads, promoted, tags, hasPrivacyPolicy, licenseUrl (custom licences have no name, so license says Custom license and licenseUrl points to its text). Edge rows add storeProductId, isMature.

{
  "store": "chrome",
  "id": "ddkjiahejlhfcafbddmgiahcphecmpfh",
  "url": "https://chromewebstore.google.com/detail/ublock-origin-lite/ddkjiahejlhfcafbddmgiahcphecmpfh",
  "name": "uBlock Origin Lite",
  "summary": "An efficient content blocker. Blocks ads, trackers, miners, and more immediately upon installation.",
  "rating": 4.5,
  "ratingCount": 3641,
  "users": 21000000,
  "version": "2026.930.1227",
  "updatedAt": "2026-09-30T14:36:39.000Z",
  "createdAt": "2022-09-08T13:10:25.000Z",
  "size": "9.2MiB",
  "developerName": "Raymond Hill (gorhill)",
  "developerEmail": "ubo@raymondhill.net",
  "supportUrl": "https://github.com/uBlockOrigin/uBOL-issues",
  "privacyPolicyUrl": "https://github.com/gorhill/uBlock/wiki/Privacy-policy",
  "category": "make_chrome_yours/privacy",
  "languages": ["ar", "az", "bg", "…"],
  "permissions": ["activeTab", "alarms", "contextMenus", "declarativeNetRequest", "…"],
  "manifestVersion": 3,
  "minBrowserVersion": "122.0"
}

What each store gives and does not give:

• Chrome: users is the store's rounded figure (e.g. 21,000,000); the store hides it for a few listings (Google's own extensions among them), then it is null. developerEmail is shown by the store for most publishers. Permissions come from the published manifest. No review texts (that sub-page is closed to robots).
• Firefox: everything from the public add-ons API, including license, downloadUrl (the signed .xpi), weeklyDownloads and the promoted badges (recommended, line). users is average daily users. size is the .xpi size.
• Edge: the store API; developerEmail, createdAt and size are not published, so they stay null. Search results carry no user count, version or permissions until their record is opened (Open extension pages, on by default).

Pricing

Pay per extension. A Chrome or Edge extension read from its own page or API is one extension with store page opened; an extension from a Firefox search / category, or a Chrome category card / Edge search result with Open extension pages off, is one extension from a listing. Duplicates within a run are delivered and charged once. Set a maximum charge per run in the run options to cap spend.

Event	Price
Extension with store page opened	$2.00 per 1,000
Extension from a listing	$1.00 per 1,000
Run start	$0.002

Tips

• Chrome category slugs are the last two parts of the store URL: productivity/tools, productivity/developer, lifestyle/shopping, make_chrome_yours/privacy, … (18 in total; an unknown slug stops the run with the full list).
• Chrome collection slugs are the last part of a https://chromewebstore.google.com/collection/... URL: 2025_favorites, gmail_extensions, ai_productivity, ai_content, dark_mode, side_panel, language_learning, games, … The store's front page links the current ones; they change over time, so an unknown slug gives a warning and the run goes on.
• Edge search can be sorted by relevance, top rated or most popular (the store's own three orders).
• Firefox category slugs are as in the AMO URL: privacy-security, shopping, tabs, search-tools, social-communication, download-management, …
• To watch competitors, paste their extension URLs from all three stores in one run and schedule it: every row carries version, updatedAt, users and rating, so a diff of two runs shows releases and growth.
• The actor opens at most 4 store pages at once and backs off automatically if a store answers 429.