Get Chrome Web Store dataset metrics API

Endpoint facts

Method

GET

API path

/datasets/chrome-extensions/metrics

Auth

apiKey

Credits

1 credit/request

Platform

Datasets

Response schema

#/definitions/datasets.chromeExtensionMetricsResponseDoc

Overview

Returns chart-ready coverage, adoption, rating, permission, privacy and recent-change aggregates for the stored Chrome Web Store dataset. Days enum: `7`, `30`, `90`. Developers commonly use this endpoint for repeatable dataset search, filtering, facets, local business enrichment, analytics, exports, and internal tools that need structured records beyond the limited manual refinement available in the Google Maps app. Authentication uses the x-api-key header, usage is metered with the credit cost shown on this page, and the request does not trigger live scraping or proxy routing.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint reads stored indexed dataset records. It does not execute a live upstream Google Maps request, browser session, or proxy-routed scraping job.

• Data source: stored Crawlora dataset records
• Proxy strategy: no proxy routing is applied
• Browser rendering: not used for dataset search or lookup requests
• Live scraping: not triggered by dataset list, search, nearby, facet, or detail endpoints
• Validation: invalid filters, coordinates, pagination, and enum values return documented errors
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

- `summary` reports current totals, developer-name and developer-email coverage, and the most recent crawl timestamp. - `item_types`, `manifest_versions`, `user_bands`, `rating_bands`, `review_bands`, and `risk_signals` are complete chart series. - `top_categories` and `top_developers` include item counts and summed displayed users; `top_permissions` counts declared permissions across items. - `changes.daily` fills empty calendar days within the selected window, while `changes.types` counts the change categories observed. - A not-yet-populated index returns zero totals and empty bucket arrays rather than an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "dataset": "chrome-extensions", "generated_at": "2026-07-14T08:00:00Z", "days": 30, "summary": { "total": 966, "total_users": 10232794, "total_ratings": 36524, "average_rating": 4.4341, "privacy_policies": 440, "named_developers": 774, "developer_emails": 104 }, "item_types": [ { "value": "extension", "count": 693 }, { "value": "theme", "count": 238 } ], "risk_signals": [ { "value": "Broad host access", "count": 146 }, { "value": "Collects data", "count": 198 } ], "top_categories": [ { "value": "productivity/tools", "count": 256, "users": 1200000 } ], "top_developers": [ { "value": "Example Publisher", "count": 12, "users": 250000 } ], "changes": { "total": 1, "types": [{ "value": "status", "count": 1 }], "daily": [{ "date": "2026-07-14", "count": 1, "users_delta": 0, "rating_count_delta": 0 }] } } } ```

Error behavior

Crawlora does not silently return invalid dataset search results when filters, pagination, coordinates, or stored record lookups cannot be satisfied.

When possible, Crawlora returns structured error context so your integration can adjust filters, page size, location inputs, or lookup identifiers.

Related