/appbrain/apps

POST /api/appbrain/apps

Price: 10 credits

Get AppBrain app details by Android package name, AppBrain app URL, or Google Play URL

How to use it

Get full AppBrain market-intelligence for an Android app by its package name (or an AppBrain / Google Play app URL). Returns name, developer, category, icon, description, version, size, rating and rating count, price, content rating, minimum Android version, whether it shows ads, total and recent download estimates, Google Play ranking status and per-country/category ranking positions, screenshots, the first-published and last-updated times, the detected third-party SDKs/libraries used by the app (the distinctive AppBrain signal), and the requested Android permission groups.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• app string required — Android package name, an AppBrain app URL, or a Google Play app URL (examples: "com.whatsapp", "com.spotify.music", "https://www.appbrain.com/app/whatsapp-messenger/com.whatsapp", "https://play.google.com/store/apps/details?id=com.whatsapp"; minLength: 1)

Response

• @type string (default: "AppbrainApp")
• package_name string required
• name string required
• developer string nullable
• developer_url string nullable
• category string nullable
• image string nullable
• description string nullable
• version string nullable
• size string nullable
• rating number nullable
• rating_count integer nullable
• price number nullable
• price_currency string nullable
• is_free boolean nullable
• content_rating string nullable
• min_android_version string nullable
• has_ads boolean nullable
• ranking_status string nullable
• total_download_count integer nullable
• recent_download_count integer nullable
• library_count integer nullable
• permission_count integer nullable
• published_at integer nullable
• updated_at integer nullable
• google_play_url string nullable
• screenshots array (default: [])
• libraries array (default: [])
  • @type string (default: "AppbrainLibrary")
  • id string required
  • name string required
  • alias string nullable
• permissions array (default: [])
  • @type string (default: "AppbrainPermissionGroup")
  • group string required
  • items array (default: [])
• rankings array (default: [])
  • @type string (default: "AppbrainAppRankingEntry")
  • rank integer required
  • country string nullable
  • category string nullable
  • list_type string 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 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.