/appstore/apps/charts

POST /api/appstore/apps/charts

Price: 10 credits

Get an Apple App Store top-chart ranking by storefront and optional category

How to use it

Get an Apple App Store chart ranking (top free, top paid, top grossing, or newest apps) for a given storefront country. Each entry includes the app name, id and bundle id, developer, icon, category, price and currency, and release date. Optionally restrict the chart to a single app category, and choose how many ranked apps to return.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• chart_type string required — App Store chart (one of: "topfreeapplications", "toppaidapplications", "topgrossingapplications", "newapplications", "newfreeapplications", "newpaidapplications")
• count integer required — Max number of results (min: 1; max: 200)
• country string — App Store storefront country (default: "us"; one of: "us", "gb", "ca", "au", "de", "fr", "it", "es", "nl", "se", "jp", "kr", "cn", "in", "br", "mx", "ru", "tr", "pl", "ae", "sa", "sg", "hk", "tw", "id", "th", "vn", "ph", "my", "za")
• category string nullable — Restrict the chart to a single app category (one of: "6014", "6000", "6001", "6002", "6003", "6004", "6005", "6006", "6007", "6008", "6009", "6010", "6011", "6012", "6013", "6016", "6017", "6018", "6020", "6021", "6022", "6015", "6023", "6024", "6025", "6026", "6027")

Response

• @type string (default: "AppstoreChartEntry")
• id integer required
• bundle_id string nullable
• name string required
• alias string nullable
• url string nullable
• image string nullable
• developer_id integer nullable
• developer_name string nullable
• developer_url string nullable
• category string nullable
• category_id integer nullable
• price number (default: 0)
• formatted_price string nullable
• currency string nullable
• is_free boolean (default: false)
• rights string nullable
• released_at string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.