Skip to content

Structured App Store data: send queries. Single lookup, 1 credit per successful call.

GET · POST1 credit / successful callSingle lookup
GEThttps://api.scrapier.io/api/v2/app-store-keywords-suggestion/Open in Playground

Call GET /api/v2/app-store-keywords-suggestion/ with queries. The results are in data.result. 2 optional parameters refine the call (see Parameters).

Terminal window
curl -G "https://api.scrapier.io/api/v2/app-store-keywords-suggestion/" \
-H "X-API-Key: YOUR_API_KEY" \
--data-urlencode "queries=light" \
--max-time 210
NameTypeRequiredDefaultDescription
X-API-Key headerstringyes—Your API key from the dashboard.
queriesstringyese.g. lightSearch keyword. Lookup endpoint -- next_cursor null.
max_itemsintegerno50No description in the catalog yet.
Advanced
NameTypeDefaultDescription
use_proxybooleantrueRoute the request through Scrapier's residential proxy pool. Default: true. Leave as is unless support tells you otherwise.
raw_databooleanfalseWhen true, the response carries the full raw upstream payload(s) the scraper received (GraphQL / JSON API bodies, HTML, embedded JSON-LD -- exactly as the platform returned them) under raw_responses, in place of the formatted items. When false (default) you get the formatted output. Pagination (cursor / next_cursor) works the same in both modes.
{
"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
}
}

Sample from the live catalog; arrays trimmed to 3 items. Results are in data.result.

FieldTypeExampleDescription
queriesstringlight—
resultobject{…}The results.
next_cursornullnullPass back as cursor for the next page. null on the last page.
result.querystringlight—
result.successbooleantrue—
result.suggestionsarray[3 items]—

Returns everything in one call; next_cursor is always null.

Failed calls are free. Branch on the HTTP status and read the message from error (or detail). Full details in Errors.

StatusMeaningRetry?Charged?
400Bad or missing input.No — fix the paramsNo
401 / 403Missing, invalid or revoked API key.No — fix the keyNo
402Out of credits (body has balance).No — top upNo
404Unknown endpoint slug.No — check the slugNo
429 / 503Busy or throttled.Yes — after Retry-AfterNo
5xxTarget site or upstream failure, or timeout.Yes — with backoffNo
  • The response data carries its own success field from the scraper. The outer success is what counts: an HTTP 200 with outer success: true is billed, even if the inner field says otherwise.
  • App Store App Info — Structured App Store data: send urls. Single lookup, 1 credit per successful call.
  • Apple App Store — Structured App Store data: every input is optional. Cursor-paginated, 1 credit per successful call.
  • Apple App Store Review Scraper — Structured App Store data: send urls. Cursor-paginated, 1 credit per successful call.