Crawlora Docs
Sync app reviews from app stores, normalize ratings and text, tag feedback topics, and monitor competitors.
Sync app reviews from app stores, normalize ratings and text, tag feedback topics, and monitor competitors.
Only endpoints that exist in the generated endpoint metadata are linked here. Missing optional endpoints are intentionally omitted.
/appstore/reviewsReturns one page of customer reviews for an App Store app, identified by `id` (numeric track ID) or `app_id` (bundle ID). `page` runs 1 to 10 and `sort` is `mostRecent` (default) or `mostHelpful`. Reviews carry `score`, `title`, `text`, `version`, `user_name` and `updated`. Returns 503 when reviews cannot be retrieved, and 404 when the app is not in that `country` storefront.
/googleplay/reviewsReturns Google Play reviews for an app by `app_id`. `sort` is `newest` (default), `helpfulness` or `rating`, and `num` is up to 1000 per request (default 100). Each review has its text, score, date, thumbs-up count, app version and any developer reply. Pass `next_pagination_token` back to continue.
| Field | Notes |
|---|---|
| app_id | Workflow field; map to exact endpoint response fields from endpoint docs. |
| platform | Workflow field; map to exact endpoint response fields from endpoint docs. |
| review_id | Workflow field; map to exact endpoint response fields from endpoint docs. |
| rating | Workflow field; map to exact endpoint response fields from endpoint docs. |
| title | Workflow field; map to exact endpoint response fields from endpoint docs. |
| text | Workflow field; map to exact endpoint response fields from endpoint docs. |
| author | Workflow field; map to exact endpoint response fields from endpoint docs. |
| version | Workflow field; map to exact endpoint response fields from endpoint docs. |
| reviewed_at | Workflow field; map to exact endpoint response fields from endpoint docs. |
| topic | Workflow field; map to exact endpoint response fields from endpoint docs. |
This example uses the real Retrieve App Store reviews endpoint. Exact request fields come from the endpoint metadata.
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/appstore/reviews?country=us&page=1&sort=mostRecent&lang=en" \
-H "x-api-key: $CRAWLORA_API_KEY"Use endpoint detail pages for exact response schemas. This recipe does not invent response fields.
{
"code": 200,
"msg": "OK",
"data": [
{
"id": "review-1",
"user_name": "App Store User",
"user_url": "https://itunes.apple.com/us/reviews/id123456789",
"version": "1.2.3",
"score": 5,
"title": "Helpful assistant",
"text": "Great for writing and research.",
"url": "https://itunes.apple.com/us/review?id=987654321",
"updated": "2026-06-12T01:00:00-07:00"
}
]
}Write reviews to JSONL for batch analysis or a database table keyed by platform and review ID.
Estimate usage by multiplying requests by endpoint credit cost. The table below only shows real credit costs available from the billing constants.
| Endpoint | Credit cost | Docs |
|---|---|---|
| Retrieve App Store reviews | 3 credits/request | /docs/app-store/appstore-reviews |
| Retrieve Google Play reviews | 3 credits/request | /docs/google-play/googleplay-reviews |
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 termsUse this recipe for workflow shape, then rely on endpoint reference pages for exact paths, request schemas, response schemas, and credit costs.