Back to APIs
Apple App Store public data

Apple App Store APIs

Collect public Apple App Store app details, category rankings, and reviews from known store URLs as normalized app and review records.

Available Apple App Store APIs

Use App Detail for known listings, Rankings for public chart URLs, and App Reviews for public feedback from known app URLs.

What Apple App Store data can you retrieve?

The current endpoint preserves public listing fields in the shared app result schema and leaves unavailable values empty.

App identity

Retrieve available app IDs, names, developers, categories, source URLs, and descriptive text.

Visible listing signals

Keep available rating, review-count, pricing, rank, and publication context as point-in-time values.

Media and observation time

Store available listing media with collected_at so records retain their observation context.

Apple App Store API contract overview

Each endpoint uses known public URLs and the standard asynchronous task-result reader.

EndpointInputSource scope
App DetailOne or more product-page URLsAt most one normalized app record per submitted URL
RankingsCategory or ranking URLs and optional results_limitApps exposed by the submitted charts
App ReviewsApp URLs and optional results_limitPublic reviews for the submitted apps

How the Apple App Store API works

All three endpoints use the standard asynchronous task workflow.

  1. 1. Submit known listing URLs

    Choose the matching endpoint, POST its required urls array and optional result limit, and save task_id.

  2. 2. Track the task

    Poll /v1/tasks/{task_id} until the task succeeds or fails.

  3. 3. Read stored records

    Read data.results.items and follow next_cursor only while has_more is true.

Retrieve public app listing metadata

Authenticate with a SocQ API key and submit one or more known Apple App Store product-page URLs.

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

Common Apple App Store API use cases

Catalog enrichment

Add normalized identity, descriptive metadata, developer, category, pricing, media, and source context to known app records.

Listing comparison

Compare available metadata, visible ratings, review counts, and pricing across a prepared URL set.

Snapshot monitoring

Store repeated results with collected_at to compare public listing fields over time.

Limits and public-data policy

Apple App Store results are point-in-time public listing records and do not provide publishing or account-management functions.

  • Every submitted URL must resolve to apps.apple.com or one of its subdomains.
  • The APIs accept known store URLs rather than keywords or bundle IDs alone.
  • App Detail saves at most one result per URL, while Rankings and App Reviews accept a task-wide results_limit from 1 to 2,000.
  • Task-result cursors only page through records already stored by SocQ.
  • Final billing is 0.15 credits per stored result with a zero-credit base; estimation depends on the selected endpoint.

Apple App Store API frequently asked questions

What are the Apple App Store APIs?

The Apple App Store APIs retrieve app details, collect category rankings, and collect public app reviews from known store URLs.

Can I search for apps by keyword?

No. The current requests start from non-empty arrays of known Apple App Store product or chart URLs.

Does the source support pagination?

There is no caller-facing source cursor. Task-result cursors only paginate records already stored after collection.

How is collection billed?

Each stored result costs 0.15 credits. Final charges use actual result count; estimation depends on the selected endpoint.

Bring public profiles, content, and engagement data from different platforms into one workflow to track brands, creators, and topics and run cross-platform monitoring and analysis more efficiently.