/xiaomigetapps/cn/apps

POST /api/xiaomigetapps/cn/apps

Price: 5 credits

Get a mainland-China Xiaomi app store app by its Android package name

How to use it

Look up one app on the mainland-China Xiaomi storefront (app.mi.com), which is a separate catalogue from the global GetApps one — an app present in one is often absent from the other, and the two share no identifiers except the Android package name. Text comes back in Chinese, since that is what the storefront publishes. rating is rescaled to the same 0-5 range the global endpoint uses, and it comes from a half-star display value, so treat it as coarse. permissions here are the storefront's own Chinese permission wording, not Android permission constants.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• package_name string required — Android package name, or a Xiaomi app store (app.mi.com) app URL (examples: "com.tencent.mm", "com.tencent.tmgp.sgame", "https://app.mi.com/details?id=com.hottagames.hotta.mi"; minLength: 1)

Response

• @type string (default: "XiaomigetappsCnApp")
• package_name string required
• app_id string nullable
• name string nullable
• developer string nullable
• category string nullable
• category_id string nullable
• devices array (default: [])
• version string nullable
• apk_size integer nullable
• updated_date string nullable
• rating number nullable
• rating_count integer nullable
• privacy_policy_url string nullable
• download_url string nullable
• url string nullable
• image string nullable
• screenshots array (default: [])
• description string nullable
• changelog string nullable
• permissions array (default: [])
  • @type string (default: "XiaomigetappsCnPermission")
  • name string required
  • description 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 — No app with this package name exists on the mainland-China storefront 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.