/xiaomigetapps/cn/apps/categories

POST /api/xiaomigetapps/cn/apps/categories

Price: 10 credits

List apps in one category of the mainland-China Xiaomi app store

How to use it

Walk one category of the mainland-China Xiaomi storefront. The storefront files each app under a single category but its listings leak: asking for one game sub-category also returns some apps filed under neighbouring ones, so check each row's own category rather than assuming it matches what you asked for. Names and summaries are Chinese. Each row is a thin listing card — pass package_name to the China app endpoint for the full record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Storefront category. Members prefixed with game_ are sub-categories of games; games itself returns apps drawn from all of them (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)

Response

• @type string (default: "XiaomigetappsCnAppShort")
• package_name string required
• app_id string nullable
• name string nullable
• publisher string nullable
• developer_id string nullable
• category string nullable
• category_id string nullable
• tag string nullable
• apk_size integer nullable
• rating number nullable
• rating_count integer nullable
• summary 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.