prism

Cross-store app review intelligence (Google Play + App Store): translated, clustered, sentiment-scored.

One call returns a topic-clustered, sentiment-classified review report across Google Play and the App Store: per-store rating summary (listed aggregate), topic clusters, a pooled daily sentiment timeline, extracted feature requests, and developer-response rate, plus every raw review on the shared canonical Review shape. Resolve by store app_id (com.spotify.music / 324684580) or by query to auto-resolve the top app on each requested store. Sync by default; streams Server-Sent Events when the client sends Accept: text/event-stream (the review legs plus clustering run ~30s). Single-store calls are 10 credits; both stores 15.

get/prism/app-reviews

Request

Base URL: https://www.socialcrawl.dev/v1
URL: https://www.socialcrawl.dev/v1/prism/app-reviews
Auth: API key in header x-api-key

Query parameters

google_play_idstring

Google Play package name (e.g. com.spotify.music). (one of: google_play_id, app_store_id, query; at least one required)

app_store_idstring

App Store numeric app id (e.g. 324684580). (one of: google_play_id, app_store_id, query; at least one required)

querystring

App name to auto-resolve the top hit on each requested store (when no id is given). (one of: google_play_id, app_store_id, query; at least one required)

countrystring

Storefront country, as a location name or numeric code (look one up with GET /v1/app_store/locations or GET /v1/google_play/locations). Defaults to United States.

languagestring

Language code (e.g. en).

depthinteger

Reviews per store (default 150 Google / 50 Apple, max 600). The App Store returns ~50 at depth 40.

storesstring

CSV subset of google_play,app_store. Defaults to whichever ids/query resolve.

includestring

CSV of topics,sentiment_timeline,feature_requests,responses (default all). Omitting topics+feature_requests skips the LLM step.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "prism",
  "endpoint": "/v1/prism/app-reviews",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.