/oppo/apps/batch

POST /api/oppo/apps/batch

Price: 1 credit

Get up to 200 OPPO App Market apps in one call, by Android package name

How to use it

Resolve many package names against the OPPO / HeyTap App Market storefront in one call. The result is usually shorter than the input: packages the storefront does not carry are simply absent, and so are apps that ship an expansion file alongside the APK, which this surface drops even though /oppo/apps resolves them. Rows keep the order you asked in, so match them back by package_name and re-ask /oppo/apps for anything missing. An input where nothing resolves is an empty 200, not an error. These records come from the storefront's list view, so description, screenshots, video, expansion_file and the category fields are absent here; call /oppo/apps for any app you need those for. 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. compatibility_tester is an OPPO store staff handle attached to the listing, not the developer.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• package_names array required — Android package names to look up in one call (examples: ["com.whatsapp","com.truecaller","com.facebook.katana"]; minItems: 1; maxItems: 200)

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 — 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.