POST /api/huaweiappgallery/apps/search/suggestions
Price: 1 credit
Get the search terms Huawei AppGallery completes a partial query with
Completions for a partial query, in the store's own order, useful for turning a vague intent into a term worth passing to /huaweiappgallery/apps/search. They mix category phrasings with concrete app names, so a completion is a query to run rather than an app to report, and a fragment the store does not recognise still comes back with a handful of guesses. The store returns its own short list of about half a dozen terms at most; count only caps that list further down, it cannot ask for more than the store offers. They are drawn from the same catalog /huaweiappgallery/apps/search reads, so a completion taken from here does resolve to results there.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)query string required — Partial search term to complete (examples: "whats", "photo", "bank"; minLength: 1)count integer required — Max number of suggestions to return (min: 1)@type string (default: "HuaweiAppgallerySearchTerm")term string requiredsection string nullable422 — 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.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.