/huaweiappgallery/apps

POST /api/huaweiappgallery/apps

Price: 5 credits

Get one Huawei AppGallery app

How to use it

The Android package name is returned on the record but is not accepted as input anywhere on the store, and searching for it is not a reliable substitute: measured live against the real search backend over 91 packages harvested from that same backend's catalog, matching the package against /huaweiappgallery/apps/search results found the exact package anywhere on page one only about 29% of the time, and about 3% of those queries returned zero rows at all. A caller holding only a package name has no reliable way in through this store. This is the endpoint to trust for ratings: it reads the storefront a European visitor sees, while /huaweiappgallery/apps/search reads the store's global catalog and its rows carry a different rating for the same app, or none. reviews stops at the sixteen the store prints on the listing, so take review_count for the real total instead of counting the list. Many apps genuinely have no rating, and a null there is the store's silence rather than a zero score. Description, tagline, announcement and the review text are whatever publishers and reviewers wrote, so a record can come back in German, Chinese or Russian.

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)
• app string required — AppGallery app id, or an AppGallery app URL carrying one (examples: "C101585519", "https://appgallery.huawei.com/app/C101585519", "https://appgallery.cloud.huawei.com/ag/n/app/C101585519"; minLength: 1)

Response

• @type string (default: "HuaweiAppgalleryApp")
• id string required
• url string required
• name string required
• package_name string nullable
• description string nullable
• tagline string nullable
• editor_review string nullable
• announcement string nullable
• developer string nullable
• image string nullable
• images array (default: [])
• videos array (default: [])
  • @type string (default: "HuaweiAppgalleryAppVideo")
  • url string required
  • image string nullable
  • duration_seconds integer nullable
  • resolution string nullable
• version string nullable
• version_code string nullable
• version_release_date string nullable
• size_bytes integer nullable
• size_text string nullable
• sha256 string nullable
• md5 string nullable
• target_sdk integer nullable
• min_age integer nullable
• age_rating string nullable
• age_rating_image string nullable
• is_game boolean nullable
• price number nullable
• price_text string nullable
• has_in_app_purchases boolean nullable
• availability_note string nullable
• rating number nullable
• rating_count integer nullable
• rating_distribution array (default: [])
  • @type string (default: "HuaweiAppgalleryRatingBucket")
  • stars integer required
  • rating_count integer required
• review_count integer nullable
• reviews array (default: [])
  • @type string (default: "HuaweiAppgalleryAppReview")
  • author string nullable
  • image string nullable
  • text string nullable
  • rating number nullable
  • created_at integer nullable
• install_count integer nullable
• install_count_text string nullable
• web_url string nullable
• privacy_policy_url string nullable
• safety_labels array (default: [])
• permissions array (default: [])
  • @type string (default: "HuaweiAppgalleryPermission")
  • group string required
  • name string required
  • description string nullable
• hms_sdk object nullable
  • @type string (default: "HuaweiAppgalleryHmsSdk")
  • core_version string nullable
  • account_version string nullable
  • in_app_purchases_version 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 id in the AppGallery catalog. 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.