POST /api/huaweiappgallery/apps/collections
Price: 20 credits
Get the apps in Huawei AppGallery's editorially curated collections
Call it without a collection first: that returns the store's front page across every collection it is currently running, and the collection field on each row gives you the exact names to pass back. Naming one instead walks that collection to its end, a few hundred apps rather than the handful the front page shows. The store retires and renames collections, and the set is read from the storefront on each call, so take the name from a fresh unfiltered call rather than from an earlier answer.
access-token string requiredtimeout 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)collection string nullable — Name of one collection, as printed in the collection field of an unfiltered call (examples: "Top rated apps", "New games we love"; minLength: 1)@type string (default: "HuaweiAppgalleryCollectionApp")id string requiredurl string requiredname string requiredpackage_name string nullabletagline string nullableimage string nullablecategory string nullableversion string nullableversion_code string nullablesize_bytes integer nullablesize_text string nullablesha256 string nullablemd5 string nullabletarget_sdk integer nullablemin_age integer nullableprice number nullablerating number nullablerating_count integer nullableinstall_count integer nullableinstall_count_text string nullablehas_video boolean nullablecollection string required422 — 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 — This storefront is not running a collection with that name. 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.