POST /api/google/play/apps
Price: 10 credits
Get full Google Play app details by package name. Includes rating, installs, price, screenshots.
Get full details of a Google Play app by its package name (e.g. 'com.whatsapp'). Returns name, developer, summary, description, rating, rating count, per-star rating histogram, install count, price, currency, in-app purchase price range, version, content rating, category, whether it contains ads, top-chart placement (chart name and rank), requested permissions, data-safety labels, release date, last update date, what's new, icon, cover image, screenshots, website, support email and privacy policy.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)package string required — App package name (examples: "com.whatsapp"; minLength: 1)@type string (default: "GooglePlayApp")package string requiredname string requireddeveloper string nullabledeveloper_id string nullabledeveloper_url string nullablesummary string nullabledescription string nullablerating number nullablerating_count integer nullableinstall_count integer nullableinstall_count_display string nullableprice number nullablecurrency string nullableversion string nullablecontent_rating string nullablecategory string nullablecategory_id string nullablehas_ads boolean (default: false)chart_label string nullablechart_rank string nullablereleased_at string nullableupdated_at string nullablewhats_new string nullablein_app_purchase_price_range string nullablerating_histogram object nullable* integerpermissions array (default: [])@type string (default: "GooglePlayPermission")group string nullablepermissions array (default: [])data_safety array (default: [])@type string (default: "GooglePlayDataSafety")label string requireddetail string nullableimage string nullablecover string nullablescreenshots array (default: [])website string nullableemail string nullableprivacy_policy_url 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 — App not found for the given package name. 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.