POST /api/xiaomigetapps/cn/apps/ranking
Price: 20 credits
Read the mainland-China Xiaomi app store ranking, for the whole store or one category
Read the storefront's ranking, which is where its own notion of popularity lives — nothing else on this platform exposes an ordered list. rank is the storefront's position, not something computed here. The ranking stops at 108 entries per category and the storefront states no basis for the order, so do not present it as an install or revenue chart. A few ranked packages have no detail page left, so the China app endpoint answers 412 for them while they stay in this list. Each row is a thin listing card — pass package_name to the China app endpoint for the rest.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)category string nullable — Restrict the ranking to one category. Left unset, the ranking spans the whole store (one of: "finance", "social", "travel", "home_life", "tools", "photography", "books", "sports", "shopping", "productivity", "news", "education", "entertainment", "health", "games", "game_strategy", "game_shooter", "game_racing_sports", "game_online_rpg", "game_board", "game_fighting", "game_kids", "game_casual", "game_flight", "game_platformer", "video_and_audio", "game_tower_defense", "game_simulation")count integer required — Max number of results (min: 1; max: 108)@type string (default: "XiaomigetappsCnRankedApp")rank integer requiredpackage_name string requiredapp_id string nullablename string nullablecategory string nullablecategory_id string nullableurl string nullableimage string nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.