/huaweiappgallery/apps/recommended

POST /api/huaweiappgallery/apps/recommended

Price: 5 credits

Get Huawei AppGallery's store-wide 'Also popular' recommendation shelf

How to use it

The store's single 'Also popular' shelf, printed under every app's listing. It is not a similarity or related-apps measure and it does not depend on any particular app: across seven apps from different verticals the store returned the same row, 404 to 406 of the same 405 ids. Read it as what AppGallery is promoting store-wide right now, not as recommendations tied to one app. The row runs to several hundred entries.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• regional_catalog boolean — Read the catalog of the region the request comes from instead of the store's global one. It changes the result on /huaweiappgallery/apps/search only; the other endpoints already read a regional storefront and return the same apps either way (default: false)
• count integer required — Max number of apps to return (min: 1)

Response

• @type string (default: "HuaweiAppgalleryAppListing")
• id string required
• url string required
• name string required
• package_name string nullable
• tagline string nullable
• image string nullable
• category string nullable
• version string nullable
• version_code string nullable
• size_bytes integer nullable
• size_text string nullable
• sha256 string nullable
• md5 string nullable
• target_sdk integer nullable
• min_age integer nullable
• price number nullable
• rating number nullable
• rating_count integer nullable
• install_count integer nullable
• install_count_text string nullable
• has_video boolean 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.