App Store Scraper API
Apple App Store API: 9 endpoints for iOS app search, app detail by numeric id, user reviews, iPhone and iPad top charts, and a paginated listings database. Core endpoints cost 5 credits, the listings database 10, reference lookups 1 — 100 free credits on signup, no card. Full iOS app metadata and reviews without device farms or Mac-only tooling.
TL;DR
The App Store API by SocialCrawl returns App Store data as structured JSON — 9 endpoints behind one x-api-key, from 1 credit per call. It shares one unified schema with 43 other platforms, so the same client code works everywhere.
Where to find SocialCrawl
Try the App Store API in your browser
Type a real handle, run a real request, see the JSON SocialCrawl returns. No signup, no key — same response shape you get in production.
Try the App Store App Search API
See real data before writing a single line
What data does the App Store API return?
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Last updated July 2026
Maintained by the SocialCrawl team, reviewed July 2026
What App Store data can you get?
Every App Store endpoint uses the same response envelope, so one parser handles the whole platform. These are fields returned by current public responses, subject to each endpoint's documented cache window.
Fields you get back in a App Store response include:
- title
- url
- description
- engagement_rate_percentages
- recent_posts
- followers
- comments
- likes
- recent_posts_explanation
- id_user
- username
- is_private
- posts_details
How to scrape App Store in 3 steps
No proxies, no headless browsers, no login sessions. Send one authenticated GET request and read structured JSON back.
- 1
Get a free API key
Create an account and copy your key from the dashboard. Signup includes 100 free credits, and no card is required.
- 2
Call the App Search endpoint
Send a GET request with your key in the x-api-key header. Here is the full App Store App Search request:
curl -H "x-api-key: YOUR_API_KEY" \ "https://www.socialcrawl.dev/v1/app_store/app-search?query=photo+editor" - 3
Read the unified JSON
The response comes back in the shared SocialCrawl schema. Where the endpoint supports them and the required source inputs are present, fields such as engagement_rate and content_category are filled in too. Your client can rely on the shared envelope while treating enriched fields as optional.
Requirements and limits
Everything you need to know before your first App Store call.
- Authentication
- One API key, passed in the x-api-key request header. No OAuth flow, no app review, and no per-platform credentials to manage.
- Pagination
- List endpoints return a next_cursor and a has_more flag. Pass the cursor back to page through results, with the same contract on every platform.
- Credits
- Calls start at 1 credits and are deducted per request. Every account starts with 100 free credits, and credits never expire.
- Rate limits
- There are no artificial rate limits. Your credit balance is the only throttle, so you can run requests concurrently as fast as you need.
How much does the App Store API cost?
Simple credit-based pricing with no subscription. You pay per call, and the exact credit cost of every App Store endpoint is listed below.
| Endpoint | Credits per call |
|---|---|
| App Search | 5 credits |
| Search Suggestions | 1 credit |
| App Info | 5 credits |
| App Reviews | 5 credits |
| App List | 5 credits |
| App Listings Search | 10 credits |
| Categories | 1 credit |
| Locations | 1 credit |
| Languages | 1 credit |
Every account starts with 100 free credits, and no card is required.
At credit-pack pricing that works out to roughly £0.002 to £0.06 per call, and credits never expire.
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 44 platforms covering 10B+ monthly active users.
One schema, every platform
Query 44 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language — ready to use.
See your data before you code
Visual Data Explorer — paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}How does SocialCrawl handle 44 different platforms?
Social media scraping is hard. Schema normalization, authentication, rate limits, pagination — we handle it all before your data arrives.
Write once, query them all.
44 platforms return 44 different JSON shapes. We normalize every response into one consistent structure.
Metrics ready before you ask.
Normalized records include supported metrics such as engagement rate, estimated reach, content category, and language when the required source inputs are available.
One cursor, every platform.
Every platform paginates differently. We give you one consistent cursor-based system.
Fresh when it matters. Free on repeat.
Cache misses fetch current public data. Identical requests are cached for 2 to 30 minutes by data type and cost 0 credits on a hit; send Cache-Control: no-cache for a billed refresh.
Auth, proxies, and rate limits — handled.
Platform authentication, IP rotation, rate limit management — abstracted away. Just send a GET request.
What developers say
The unified schema saved us weeks of integration work. One parser handles every platform.
Our agents process social data from 44 platforms with zero platform-specific logic — one schema, end to end.
I paste an influencer's URL and get everything — followers, engagement rate, content categories — without touching code.
We switched from building our own scrapers. SocialCrawl handles the hard stuff, we focus on insights.
The computed fields alone — engagement_rate, estimated_reach, content_category — saved us an entire data pipeline.
How does SocialCrawl compare to iTunes Search API + DIY for App Store data?
Same App Store data, two very different paths. Auth, rate limits, schema, and cost — side by side.
| Feature | SocialCrawl | iTunes Search API + DIY |
|---|---|---|
| Authentication | One x-api-key header shared across 44 platforms | None for iTunes Search — but reviews need RSS feeds or scraping on top |
| Setup | One GET request covers search, detail, reviews, and charts | iTunes Search handles lookup well, but reviews and charts need extra DIY plumbing |
| Rate limits | Flat credit pricing with upstream handling | iTunes Search is throttled to roughly 20 calls per minute with no paid upgrade path |
| Response schema | Canonical App schema shared with Google Play | iTunes JSON differs from review RSS, which differs from chart feeds |
| Pricing | 5 credits per app call, 10 for the listings database; 100 free credits | Free, if you build and maintain the review and chart layers yourself |
| Data coverage | Search, detail, reviews, charts, listings, and reference data in one API | Lookup and search only — reviews, charts, and listings are not included |
Authentication
Setup
Rate limits
Response schema
Pricing
Data coverage
How much does App Store scraping cost?
SocialCrawl uses credit-based pricing: you pay per API call, and most App Store endpoints cost just a few credits. Every account starts with 100 free credits — no subscriptions, no compute units, no credit card required.
See pricingIs App Store scraping legal?
SocialCrawl returns publicly available App Store data. Courts have generally upheld scraping public data — most notably in hiQ v. LinkedIn — but compliance depends on your use case and jurisdiction. You are responsible for following applicable laws and platform terms.
Common App Store scraping terms
The phrases developers search for when they need App Store data, and what each one means with SocialCrawl.
- App Store scraper API
- A App Store scraper API returns App Store data as structured JSON without you running any scraping infrastructure. SocialCrawl handles the proxies, parsing, and format changes, so you call an endpoint and get clean fields back. Pricing starts at 1 credits per call.
- App Store data API
- A App Store data API is a programmatic way to read public App Store data on demand. SocialCrawl exposes 9 App Store endpoints behind one x-api-key, all sharing the same unified schema, so your integration never has to change per platform.
- scrape App Store
- To scrape App Store is to extract its public data programmatically instead of by hand. With SocialCrawl you scrape App Store by sending a single authenticated request, and the response is normalised into the same JSON shape used across every platform.
Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usDoes the Apple App Store have an API for app data?
What can the SocialCrawl App Store API do?
How do I reference an app in the App Store API?
How much does the App Store API cost?
Does it use the same schema as Google Play and other stores?
What is the best App Store scraper API?
Is there an App Store data API for reading public iOS apps?
Is scraping App Store data legal?
App Store scraping API vs the official App Store API — what's the difference?
Ask AI about SocialCrawl
Ready to start scraping App Store data?
Get your API key and access all 9 App Store endpoints in under 60 seconds.
Start for free