/xiaomigetapps/apps/charts

POST /api/xiaomigetapps/apps/charts

Price: 1 credit

List the apps the global Xiaomi GetApps storefront features on its front page

How to use it

Read the storefront's own editorial front page — the handful of apps it promotes in each of four featured categories, which is a curated shelf rather than a download or revenue ranking, so do not read it as a top-charts list. Only ES, ID, IN and RU have a front page at all; anywhere else answers 200 with an empty list. The games front page is served by two backends holding different picks, so two calls with the same arguments return overlapping but not identical sets and a row's name can come back in a language nobody asked for; key on package_name. Use the category endpoint when you want a whole category rather than its featured picks.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• vertical string — Which storefront front page to read — the apps one or the games one (default: "apps"; one of: "apps", "games")
• count integer required — Max number of results (min: 1)
• region string — Storefront region as an ISO 3166-1 alpha-2 code. Only ES, ID, IN and RU have a populated front page; every other region returns an empty list (default: "ID"; examples: "ID", "IN", "RU", "ES"; minLength: 2; maxLength: 2)
• language string — Which store-listing localisation to return. Each row's name comes back in this language where the developer published a listing in it, and falls back to the developer's default otherwise. Indonesian is the legacy code in, not id (default: "en"; examples: "en", "ru"; minLength: 2)

Response

• @type string (default: "XiaomigetappsAppShort")
• package_name string required
• app_id string nullable
• name string nullable
• developer string nullable
• publisher string nullable
• category string nullable
• category_id string nullable
• region string nullable
• url string nullable
• image 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.