/oppo/apps

POST /api/oppo/apps

Price: 1 credit

Get an OPPO App Market app by its Android package name

How to use it

Look up one app in the OPPO / HeyTap App Market storefront by Android package name; a Google Play or market:// URL is accepted and only the package id inside it is read, nothing is fetched from Google. The storefront is OPPO's international (India / South-East Asia) catalog, so many globally famous apps are absent from it and return 412 — that says nothing about the app existing elsewhere. A 412 is also not always final: some listings answer only intermittently, so a second call can return an app the first one did not. package_name is the only input that resolves: the numeric app_id and version_id in the response are OPPO-internal and are not accepted back here. Treat rating as approximate — the store serves a flat 4.8 both for unrated apps and, on some calls, in place of an app's real average, so a 4.8 alongside a large rating_count may still be the placeholder. category is OPPO's own taxonomy, not Google Play's; subcategory follows Google Play's category vocabulary almost verbatim, with a handful of exceptions such as 'Sports Game' and 'Personal Loans'. download_url and expansion_file.url both address OPPO's download gateway, which answers 403 to an ordinary HTTP client rather than serving the file — expansion_file, when present, names a second file the app needs on top of the APK, but its url is not fetchable through us either.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• package_name string required — Android package name, or a Google Play / market:// app URL carrying one (examples: "com.whatsapp", "com.truecaller", "https://play.google.com/store/apps/details?id=com.facebook.katana"; minLength: 1)

Response

• @type string (default: "OppoApp")
• 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
• description string nullable
• developer string nullable
• is_game boolean nullable
• category string nullable
• category_id integer nullable
• subcategory string nullable
• subcategory_id integer nullable
• category_rank integer nullable
• rank_label string nullable
• rank_score number nullable
• is_paid boolean (default: false)
• download_url string nullable
• video string nullable
• compatibility_tester string nullable
• compatibility_tester_image 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
• screenshots array (default: [])
  • @type string (default: "OppoAppScreenshot")
  • url string required
  • width integer nullable
  • height 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 — App not found in the OPPO App Market 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.