# Chrome Web Store Extension Scraper (`datamule/chrome-extension-scraper`) Actor

Scrape Chrome Web Store extension details — name, users, rating, version, category, developer — by ID or URL. The official CWS API was retired; this fills the gap. Pay per extension.

- **URL**: https://apify.com/datamule/chrome-extension-scraper.md
- **Developed by:** [Datamule](https://apify.com/datamule) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 extension scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Chrome Web Store Extension Scraper

Export public Chrome extension metadata to CSV or JSON for inventories, vendor review and market research. Supply extension IDs or detail URLs; no browser installation, login or API key is required.

### Try one listing

```json
{
  "extensions": ["aapbdbdomjkkjkaonfhkkikfgjllcleb"]
}
```

This example uses Google Translate. It replaces the previous uBlock Origin example, which returned a generic Store page rather than usable listing metadata during verification. The one-listing example has a maximum Actor event charge of **US$0.002** at the FREE-tier list price. Apify platform charges are separate; paid-tier event prices may be lower.

### Real output preview

Selected fields from the public Google Translate listing captured on September 9, 2026:

```json
{
  "extensionId": "aapbdbdomjkkjkaonfhkkikfgjllcleb",
  "name": "Google Translate",
  "users": 35000000,
  "rating": 4.2,
  "version": "2.0.17",
  "updated": "July 2, 2026",
  "category": "productivity"
}
```

These are observations, not fixed expected values: listings and ratings can change. Source fields that are unavailable in recognized markup remain `null`.

### Inputs

| Field | Required | Accepted format | Behavior |
|---|---|---|---|
| `extensions` | Yes | Non-empty array of 32-letter IDs (`a`–`p`) or Chrome Web Store detail URLs containing an ID | Console prefill is the Google Translate ID above. IDs are processed sequentially. There is no schema list-length cap; keep your first run small. Duplicate IDs are not automatically removed. |

Missing or empty input is rejected. Invalid IDs and unavailable listings produce no result rows. If no usable extension metadata is found, the run fails clearly rather than returning a successful empty or generic Store-page result. A generic `Chrome Web Store` page is not a billable extension.

### Output fields

| Field | Meaning |
|---|---|
| `extensionId`, `url` | Extension identifier and canonical Store URL |
| `name`, `description`, `icon` | Public listing identity, summary and image |
| `users`, `rating`, `ratingCount` | Public adoption and rating figures where recognized |
| `version`, `updated` | Version and listing update date |
| `category`, `developer` | Category and developer/author where exposed in recognized markup |

Fields can be null. A null developer, rating count or date is not itself evidence of an unsafe extension. The Actor does not inspect permissions, extension code or runtime behavior and does not provide a security verdict.

### Pricing

One `extension` event per returned extension row. FREE-tier list price: **US$0.002 per result / US$2 per 1,000 results**. Current paid-plan event discounts are displayed on the Actor pricing page. Infrastructure charges are separate. Use a short ID list and an explicit maximum-charge setting for initial trials; do not repeat IDs unless repeated observations are intended.

### Recurring use

Reuse a saved task with the same ID list to collect later snapshots of versions, update dates, public user counts and ratings. Export each dataset and compare by `extensionId` in your own workflow. The Actor returns current observations; it does not store a cross-run historical index or generate change alerts by itself.

### Source and limitations

The Actor makes plain HTTP requests to public Chrome Web Store detail pages. It does not log in, access private browser data, download extension packages or call developer-console APIs. Removed, unlisted, region-blocked or unavailable listings may return no usable result; Store markup changes can affect extraction. Use the data in line with Store terms and applicable law, and treat publisher and adoption details as public listing claims rather than independently verified facts.

### Troubleshooting

- **No results:** confirm the listing still opens publicly. Removed listings may return HTTP200 with a generic Store page; that is rejected.
- **Missing version/date:** the source may omit the field or change its markup. Missing fields remain null.
- **Input rejected:** provide a non-empty `extensions` array using IDs or detail URLs.
- **Need a security review:** use a dedicated scanner or human review. This Actor exports public metadata only.

# Actor input Schema

## `extensions` (type: `array`):

Chrome Web Store extension IDs (32 letters) or full detail URLs. e.g. aapbdbdomjkkjkaonfhkkikfgjllcleb or https://chromewebstore.google.com/detail/google-translate/aapbdbdomjkkjkaonfhkkikfgjllcleb

## Actor input object example

```json
{
  "extensions": [
    "aapbdbdomjkkjkaonfhkkikfgjllcleb"
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "extensions": [
        "aapbdbdomjkkjkaonfhkkikfgjllcleb"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datamule/chrome-extension-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "extensions": ["aapbdbdomjkkjkaonfhkkikfgjllcleb"] }

# Run the Actor and wait for it to finish
run = client.actor("datamule/chrome-extension-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "extensions": [
    "aapbdbdomjkkjkaonfhkkikfgjllcleb"
  ]
}' |
apify call datamule/chrome-extension-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datamule/chrome-extension-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ZdmJ9IJC4B9Ikjlqd/builds/xTcX68r2AF6IOxVSd/openapi.json