Google Play App Detail API

Google Play App Detail

Features

• Known-URL batch boundarySubmit one or more play.google.com app URLs for direct detail lookup without turning the request into keyword discovery.
• Listing identity and copyNormalize the package identifier, app name, public store description, developer, category, source URL, and collection time.
• Visible market contextKeep available rating, review-count, install-range, price, and rank fields as nullable observations from the public listing.
• Media-ready app recordsReturn media alongside a stable app schema so listing records can move through the same asynchronous results workflow as other SocQ data.

Parameters

How to Use

Submit known Google Play URLs, track the asynchronous task, and read the normalized app records after completion.

1. Prepare a non-empty urls array containing app links whose parsed hostname is play.google.com or a supported subdomain.
2. POST the array to /v1/google-play/app-detail and save the returned task_id.
3. Poll /v1/tasks/{task_id} until the task succeeds or fails.
4. After success, read data.results.items. Follow next_cursor only when has_more is true; it pages records already stored by SocQ rather than discovering another Google Play source page.

curl -X POST "https://api.socq.ai/v1/google-play/app-detail" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://play.google.com/store/apps/details?id=com.openai.chatgpt"]}'

# Poll GET /v1/tasks/{task_id}
# Read normalized app records from data.results.items

Best Use Cases

• Enrich a known app catalog: Turn stored Google Play links into normalized package IDs, titles, descriptions, developers, categories, source URLs, and collection timestamps.
• Compare selected listings: Align available rating, review-count, install-range, price, category, and media fields across an approved set of app URLs.
• Monitor listing snapshots: Repeat lookups on a defined schedule and compare nullable listing fields with collected_at to identify point-in-time changes.

Pro Tips

• Use full Google Play app URLs and deduplicate the array before submission so the estimate reflects intentional lookups.
• Treat each input URL as eligible for at most one result, then align returned records by url or app_id because an accepted URL can still resolve to no item.
• Store rating, review count, install range, price, rank, and media defensively because public listing fields can be absent or change after collection.
• Use next_cursor only to continue reading a completed task's stored SocQ results; this detail endpoint does not expose Google Play search or source-page pagination.

Related APIs