Datasets API endpoint
Returns up to 50 app-review facet buckets ordered by count, using the same filters as `datasets_apps_reviews_search`. Page and page_size do not change the aggregation. Facet enum: `store`, `app_id`, `country`, `score`.
/datasets/apps-reviews/facetsMCP tool: datasets_apps_reviews_facets
Returns up to 50 value counts, ordered by count, over stored public App Store
and Google Play reviews. Facets honor the same filters as
datasets_apps_reviews_search.
Required facet: store, app_id, country, or score.
Optional filters: q, store, app_id, country, min_score, and sort.
Store values are ios or android; sort values are recent, score_desc,
score_asc, helpful_desc. page and page_size are accepted for contract
parity; counts cover every matching review.
Sort values are validated against the corresponding search endpoint, but do not reorder facet results; buckets are always ordered by count.
Requires the x-api-key header. Costs 1 credit. An empty dataset returns an
empty items array.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| facet | string | Yes | Facet field Allowed values: store, app_id, country, score. | store | |
| q | string | No | Full-text review query | ||
| store | string | No | Store filter: ios or android Allowed values: ios, android. | ||
| app_id | string | No | Exact store app id | ||
| country | string | No | Storefront country | ||
| min_score | integer | No | Minimum star rating, 1 through 5 | ||
| sort | string | No | Validated search sort; bucket order stays count-desc, and time-series date_desc keeps its search history scope Allowed values: recent, score_desc, score_asc, helpful_desc. | ||
| page | integer | No | Result page, 1-based | ||
| page_size | integer | No | Page size, default 20 and max 100 | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/datasets/apps-reviews/facets?facet=store&q=coffee&store=ios&country=us&sort=recent&page=1" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"msg": "OK",
"data": {
"dataset": "apps-reviews",
"facet": "score",
"items": [
{
"value": "5",
"count": 10
}
]
}
}Request schema
No body schema
Response schema
#/definitions/datasets.datasetFacetResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | datasets.DatasetFacetResponse | No | ||||
| data.dataset | string | No | ||||
| data.facet | string | No | ||||
| data.items | array | No | ||||
| data.items[].count | integer | No | ||||
| data.items[].value | string | No | ||||
| msg | string | No | OK |
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 500 | Internal Server Error | #/definitions/app.Response |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/datasets/apps-reviews/facets?facet=store&q=coffee&store=ios&country=us&sort=recent&page=1" \
-H "x-api-key: $CRAWLORA_API_KEY"