Apple App Store App Detail API

Apple App Store App Detail

Features

• Known-URL batch inputSubmit one or more apps.apple.com product-page URLs, with each cleaned URL mapped to one provider input and at most one normalized app record retained per submitted URL.
• Listing identity and descriptive metadataReturn app ID, name, description text, developer, category, source URL, and collection time in a consistent app schema.
• Visible rating and price contextPreserve available rating, review count, and structured price fields so listing records can be compared without parsing product-page text.
• Media and catalog contextKeep available listing media alongside publication and collection timestamps, while omitting schema values that the public page does not expose.

Parameters

How to Use

Submit known listing URLs, follow the asynchronous task, and read normalized app records from stored result pages.

1. Prepare one or more public Apple App Store product-page URLs whose hostname is apps.apple.com or one of its subdomains.
2. POST the urls array to /v1/apple-app-store/app-detail and save the returned task_id.
3. Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
4. Read app records from data.results.items and follow next_cursor only when has_more is true.

curl -X POST "https://api.socq.ai/v1/apple-app-store/app-detail" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://apps.apple.com/us/app/chatgpt/id6448311069"]}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor only while has_more is true

Best Use Cases

• App catalog enrichment: Attach normalized app identity, descriptive metadata, developer, category, pricing, media, and source URLs to records that already contain known App Store links.
• Listing comparison: Compare developer and category context, visible ratings, review counts, pricing, and descriptive copy across a selected URL set.
• Metadata snapshot monitoring: Store repeated results with collected_at to identify changes in names, descriptions, categories, visible ratings, pricing, and media over time.

Pro Tips

• Validate every parsed hostname against apps.apple.com and submit product-page URLs rather than search terms, bundle IDs, or store names.
• Remove duplicate URLs before submission so repeated inputs do not create redundant provider rows or duplicate app records.
• Treat rating, reviews_count, price, media, published_at, installs, and rank as nullable because a listing may expose only part of the app schema.
• Do not treat next_cursor as an upstream App Store page token; it only advances through results already stored for the completed SocQ task.

Related APIs