App Store Keywords Scraper API
Last updated: · REST · JSON
Send GET https://proxy.scrapier.io/api/v2/app-store-keywords-suggestion/?queries=light with your key in the X-API-Key header. You get the keyword lookup back as JSON. 1 credit per keyword lookup; failed calls are free.
- 1 credit per keyword lookup
- Failed calls free
- 3 parallel requests per key
Call the App Store Keywords Scraper API
Use the App Store Keywords Scraper API from your own apps, scripts or agents. You need a Scrapier account and the API key from your dashboard. Pick a language.
import requests# Replace YOUR_API_KEY with the key from your Scrapier dashboardAPI_KEY = "YOUR_API_KEY"params = { "queries": "light", "max_items": "50",}r = requests.get( "https://proxy.scrapier.io/api/v2/app-store-keywords-suggestion/", headers={"X-API-Key": API_KEY}, params=params, timeout=210,)r.raise_for_status()# The result sits under data.resultresult = r.json()["data"]["result"]print(result)
// Replace YOUR_API_KEY with the key from your Scrapier dashboardconst API_KEY = "YOUR_API_KEY";const params = new URLSearchParams({ queries: "light", max_items: "50",});const res = await fetch(`https://proxy.scrapier.io/api/v2/app-store-keywords-suggestion/?${params}`, { headers: { "X-API-Key": API_KEY }, signal: AbortSignal.timeout(210_000),});if (!res.ok) throw new Error(`HTTP ${res.status}`);const { data } = await res.json();console.log(data.result);
# One GET request. The key goes in a header, never in the URL.GET /api/v2/app-store-keywords-suggestion/?queries=light&max_items=50 HTTP/1.1Host: proxy.scrapier.ioX-API-Key: YOUR_API_KEYAccept: application/json
# Scrapier publishes an OpenAPI spec that covers every endpoint. No API key needed.curl -O https://proxy.scrapier.io/api/v2/openapi.json# Import openapi.json into Postman, Insomnia, Bruno or a code generator,# then add your key as the X-API-Key header.
# 1. Add the Scrapier MCP server to Claude Codeclaude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY"# 2. Ask your agent. It finds the endpoint with search_endpoints# and calls it with run_scrape:"Get App Store keyword suggestions for light and list the ten most useful terms"run_scrape("app-store-keywords-suggestion", {queries: "light"})
App Store Keywords Scraper API in Python
Plain requests is all you need — no SDK. Every response is typed JSON.
Install
App Store Keywords Scraper API in JavaScript
Works in Node 18+, Deno, Bun and edge runtimes with the built-in fetch.
Check your setup
App Store Keywords Scraper API over HTTP
One GET request. Auth is a single X-API-Key header.
Check your setup
App Store Keywords Scraper API OpenAPI definition
Download the spec once, then import it into the tools you already use. No key is needed to fetch it.
Download the spec
App Store Keywords Scraper API over MCP
The same endpoint is a tool call for Claude Code, Cursor and Windsurf. Same queries, same 1 credit per keyword lookup.
Install
Other ways to call it
App Store Keywords Scraper API Interactive Playground
Edit the request, watch the code update, then run it. Without a key it shows the catalog sample and bills nothing. With your key it makes a real call from your browser; the key goes only to proxy.scrapier.io and is never stored.
GET /api/v2/app-store-keywords-suggestion/?queries=lightPress Run request to send it. Without a key you get the catalog sample.
Failed calls are not billed.
The sample is the same for every input: it shows the response shape, not the account you typed.
Example response, catalog sample from 9 Nov 2026
{
"success": true,
"data": {
"queries": "light",
"result": {
"query": "light",
"success": true,
"suggestions": [
{
"keyword": "light",
"type": "suggestion",
"item": "light"
},
{
"keyword": "light",
"type": "suggestion",
"item": "lightroom"
},
{
"keyword": "light",
"type": "suggestion",
"item": "lightning tracker"
}
]
},
"next_cursor": null
}
}Data You Can Extract
App Store Keywords Scraper collects the search suggestions the App Store offers when someone types a keyword, one keyword per call. Every field below comes from the catalog sample response, as typed JSON.
Result
3 fields in the response.
- query
- success
- suggestions
Response envelope
3 fields in the response.
- success
- data.queries
- data.next_cursor
Response Schema Reference
Every field in the sample response. Field names stay the same on every call.
| Field | Type | Example | Description |
|---|---|---|---|
result.query | string | "light" | The keyword that was looked up |
result.success | boolean | true | true when the lookup worked |
result.suggestions | array | 3 items | List of suggestions, each with keyword, type and item |
success | boolean | true | true on every 200 response |
data.queries | string | "light" | Your input, echoed back |
data.next_cursor | null | null | Always null: this is a lookup endpoint with no paging |
Request Parameters Reference
| Name | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
queries | string | Yes | — | The search keyword, for example light. One per call. Required. Aliases: keyword, query | light |
max_items | integer | No | 50 | How many suggestions to return, default 50 | 50 |
use_proxy | boolean | No | true | Route through Scrapier's residential proxy pool, on by default. Leave as is | true |
raw_data | boolean | No | false | Return the raw upstream payloads under raw_responses instead of the formatted items | true |
One keyword per call: to research ten keywords, make ten calls. Booleans are the strings true or false.
Pagination in the App Store Keywords Scraper API
The App Store Keywords Scraper API is a single lookup: one call returns the whole result and there is no cursor to page through. A successful call costs 1 credit; failed calls cost 0.
Access Without App Store Login
The App Store Keywords Scraper API needs no App Store account, no login and no session cookies. You send your Scrapier key in the X-API-Key header and get JSON back. It reads public data only: what any visitor sees without logging in.
Speed, Cost and Concurrency
| Metric | Value | Source |
|---|---|---|
| Cost of a successful call | 1 credit | Scrapier catalog |
| Cost of a failed call | 0 credits | Any non-2xx response |
| Parallel requests per key | 3 | Above that: 429 with Retry-After |
| Recommended client timeout | 210 seconds | Scrapier docs, every endpoint |
Latency of the App Store Keywords Scraper API
Scrapier does not publish a latency or success-rate figure for this endpoint. Each call reads App Store at call time, so response time depends on App Store and on the size of the result. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.
Limits of the Endpoint
Honest constraints of the App Store Keywords Scraper API.
- Public data only.
- A failed call, for example a missing or unavailable keyword lookup, returns a non-2xx status and costs 0 credits.
- Data is read live at call time.
- 3 parallel requests per key; above that the API answers
429withRetry-After. - Fields App Store does not show are not returned.
Scrapier vs the Official App Store API
If you need search volume, difficulty or rank tracking, use a dedicated ASO tool; this endpoint returns suggestions only. Scrapier suits teams that want one key and one JSON shape across many platforms.
| Feature | Scrapier keyword scraper | DIY App Store scraping |
|---|---|---|
| Access needed | One Scrapier API key | Your own proxies, parser and servers |
| Which data | The search suggestions the App Store shows for a keyword | Whatever your parser extracts |
| Fields returned | 3 fields: query, success and the suggestions list | Whatever you build and maintain |
| Setup | Sign up, copy a key, send a request | Find the suggestion source, handle blocks and retries |
| Cost | 1 credit per lookup, from $1.20 per 1,000 calls | Proxy, server and engineering time |
Errors and Retry Handling
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Keyword lookup data returned in data.result | Yes | — |
| 400 | Bad or missing input | No | Check queries: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |
From the error reference. Any non-2xx response costs 0 credits.
Retry logic for the App Store Keywords Scraper API
import time, requests def get_keywords(value, key, tries=5): for attempt in range(tries): r = requests.get( "https://proxy.scrapier.io/api/v2/app-store-keywords-suggestion/", headers={"X-API-Key": key}, params={"queries": value}, timeout=210, ) if r.status_code == 429: time.sleep(int(r.headers.get("Retry-After", 2 ** attempt))) elif r.status_code >= 500: time.sleep(2 ** attempt) else: r.raise_for_status() return r.json() raise RuntimeError("gave up after retries")
Pricing and Rate Limits
| Plan | Monthly price | Keyword Lookups included | Cost per 1,000 |
|---|---|---|---|
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |
Billing rules for the App Store Keywords Scraper API
The App Store Keywords Scraper API bills 1 credit per successful keyword lookup. Failed calls, meaning any non-2xx status, cost 0 credits. Every plan allows 3 parallel requests per key. The free tier lets you try it before you pay.
Bulk Lookups and CSV
queries takes one value per call. For a list, loop and run up to 3 requests in parallel per key, then flatten each row into one CSV line.
import csv, requests from concurrent.futures import ThreadPoolExecutor values = ["light"] # your list def fetch(value): r = requests.get( "https://proxy.scrapier.io/api/v2/app-store-keywords-suggestion/", headers={"X-API-Key": "YOUR_API_KEY"}, params={"queries": value}, timeout=210, ) r.raise_for_status() out = r.json()["data"]["result"] return out if isinstance(out, list) else [out] # 3 parallel requests per key is the limit with ThreadPoolExecutor(max_workers=3) as pool: rows = [row for part in pool.map(fetch, values) for row in part] cols = ["query", "success", "suggestions"] with open("out.csv", "w", newline="") as f: w = csv.DictWriter(f, fieldnames=cols, extrasaction="ignore") w.writeheader() w.writerows(rows)
CSV export from the App Store Keywords Scraper API
query,success,suggestions
light,true,[{"keyword": "light", "type": "suggestion", "item": "light"}, {"keyword": "light", "type": "suggestion", "item": "lightroom"}, {"keyword": "light", "type": "suggestion", "item": "lightning tracker"}]AI Agent Access via MCP
MCP for the App Store Keywords Scraper API
The same endpoint is available to AI agents through the Scrapier MCP server at https://mcp.scrapier.io/mcp. One command registers it in Claude Code: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY". The agent finds the endpoint with search_endpoints and calls it with run_scrape and the endpoint id app-store-keywords-suggestion. It takes the same queries input and costs the same 1 credit per keyword lookup. Setup for every client is on the App Store Keywords Scraper MCP page.
Integration Paths by Role
n8n and Make
- Add an HTTP Request step
- GET the endpoint with your
X-API-Keyheader - Map the
data.resultfields to your columns
Loop and paginate
MCP tool in your agent
Call run_scrape with endpoint app-store-keywords-suggestion from Claude, Cursor or Windsurf. Setup is on the MCP page.
CSV and flattened JSON
Flatten each row into one CSV line, one column per field, ready for Sheets, Excel or a BI tool.
Legal and Compliance Notes
Scraping publicly available web pages is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only data any visitor can see without logging in, and search suggestions hold no personal data. Under GDPR and similar laws, you must still follow local data-protection rules for anything you store, and Apple's terms apply. Consult legal counsel if your use case is unclear. This is not legal advice; see our Terms of Use.
Frequently Asked Questions
Is there a App Store keyword lookup API?
Yes. Scrapier's App Store Keywords Scraper API returns any public keyword lookup as JSON with one GET request and an X-API-Key header. No App Store app or login.
How do I call it from Python?
Use <code>requests.get</code> on <code>https://proxy.scrapier.io/api/v2/app-store-keywords-suggestion/</code> with <code>params={'queries': 'light'}</code> and <code>headers={"X-API-Key": KEY}</code>. Read <code>r.json()["data"]["result"]</code>.
What happens when a call fails?
Any non-200 response is free. Retry 429 and 5xx with backoff; the API already retries upstream failures.
How much does it cost?
1 credit per successful call — about $1.58 per 1,000 keyword lookups on the Pro plan. Failed calls are free.
Is there an OpenAPI spec?
Yes. It needs no key and covers every Scrapier endpoint.
Related App Store APIs
Apple App Store API
One endpoint, six modes set by process: app lookup, search, developer apps, collections, reviews and performance.
Apple App Store Review API
Reviews for one app, a page at a time: author, rating, title, text, date, edited flag and developer response.
App API
One app by App Store URL or numeric ID: title, subtitle, rating and count, price, category, version and release date.
All App Store APIs
All 4 App Store endpoints.
Fetch public App Store keyword lookups as typed JSON in one request
1 credit per keyword lookup · failed calls free