Datasets API endpoint
Use Crawlora's Get a Chrome Web Store dataset item API to search or inspect stored structured datasets as JSON. This page includes request parameters, cURL examples, response schema, validation behavior, credit cost, and a Playground link for testing before integration. Dataset endpoints read indexed records and do not apply proxy routing.
/datasets/chrome-extensions/items/{id}Returns one stored extension, theme or legacy app snapshot by its 32-character Chrome Web Store id. 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.
Request parameters are generated from the active endpoint catalog. Dataset parameters filter, page, facet, or locate stored structured records; they do not configure a live scraper or proxy path.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| id (path) | string | Yes | Chrome Web Store item id | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/datasets/chrome-extensions/items/example" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint reads stored indexed dataset records. It does not execute a live upstream Google Maps request, browser session, or proxy-routed scraping job.
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.
Crawlora does not silently return invalid dataset search results when filters, pagination, coordinates, or stored record lookups cannot be satisfied.
| Status | Common failure case |
|---|---|
| 400 | Invalid input, missing required parameter, invalid enum, bad coordinate pair, or result window beyond the dataset limit |
| 404 | Requested stored dataset item is not present |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal dataset query or storage error |
When possible, Crawlora returns structured error context so your integration can adjust filters, page size, location inputs, or lookup identifiers.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 500 | Internal Server Error | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"id": "cjpalhdlnbpafiamejdnhcphjbkeiagm",
"name": "uBlock Origin",
"item_type": "extension",
"users": 13000000,
"permissions": [
"storage"
],
"has_broad_host_access": true,
"status": "active"
}
}Request schema
No body schema
Response schema
#/definitions/datasets.chromeExtensionItemResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | es.ChromeExtensionRecord | No | ||||
| data.all_permissions | array | No | ||||
| data.category | string | No | ||||
| data.collects_data | boolean | No | ||||
| data.data_collected | array | No | ||||
| data.description | string | No | ||||
| data.developer | string | No | ||||
| data.developer_email | string | No | ||||
| data.first_seen | string | No | ||||
| data.has_broad_host_access | boolean | No | ||||
| data.host_permissions | array | No | ||||
| data.icon | string | No | ||||
| data.id | string | No | ||||
| data.item_type | string | No | ||||
| data.last_crawled_at | string | No | ||||
| data.last_seen | string | No | ||||
| data.manifest_version | integer | No | ||||
| data.min_browser_version | string | No | ||||
| data.name | string | No | ||||
| data.optional_host_permissions | array | No | ||||
| data.optional_permissions | array | No | ||||
| data.permissions | array | No | ||||
| data.privacy_declarations | array | No | ||||
| data.privacy_policy | string | No | ||||
| data.rating | number | No | ||||
| data.rating_count | integer | No | ||||
| data.rating_count_delta | integer | No | ||||
| data.schema_version | integer | No | ||||
| data.screenshots | array | No | ||||
| data.size | string | No | ||||
| data.status | string | No | ||||
| data.summary | string | No | ||||
| data.trend_score | number | No | ||||
| data.updated | string | No | ||||
| data.url | string | No | ||||
| data.users | integer | No | ||||
| data.users_delta | integer | No | ||||
| data.version | string | No | ||||
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/datasets/chrome-extensions/items/example" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms