/oppo/apps/top

POST /api/oppo/apps/top

Price: 1 credit

Get the OPPO App Market top chart of apps or games

How to use it

Read the OPPO / HeyTap App Market top chart, ranked from 1. chart='app' and chart='game' are two separate charts with no package in common. It is the OPPO international (India / South-East Asia) storefront's chart, dominated by regional titles, so it is not comparable with a Google Play chart, and there is no country parameter — the same ranking is served everywhere. The app chart holds about 100 entries and the game chart about 80, so asking for more returns what exists, and even count=100 on the app chart sometimes yields slightly fewer; rank is always contiguous from 1 over what you get. Rows carry the storefront's list view: subcategory is present, but description, screenshots and the broader category are not, so pass a package_name to /oppo/apps for those. download_url addresses OPPO's download gateway and answers 403 to an ordinary HTTP client rather than serving the file. Treat rating as approximate — a flat 4.8 may be the store's placeholder rather than a real average.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• chart string — Which OPPO App Market top chart to read (default: "app"; one of: "app", "game")
• count integer required — Max number of ranked entries to return (min: 1; max: 100)

Response

• @type string (default: "OppoTopApp")
• rank integer required
• package_name string required
• name string required
• app_id integer nullable
• version_id integer nullable
• version string nullable
• version_code integer nullable
• size integer nullable
• size_text string nullable
• md5 string nullable
• checksum string nullable
• icon string nullable
• banner string nullable
• download_count integer nullable
• download_count_text string nullable
• rating number nullable
• rating_count integer nullable
• developer string nullable
• is_game boolean nullable
• subcategory string nullable
• category_rank integer nullable
• rank_score number nullable
• is_paid boolean (default: false)
• download_url string nullable
• expansion_file object nullable
  • @type string (default: "OppoAppExpansionFile")
  • url string required
  • size integer nullable
  • md5 string nullable
  • install_path string nullable
  • attachment_id integer 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.