/aptoide/apps/versions

POST /api/aptoide/apps/versions

Price: 1 credit

List all published versions of an Aptoide app by package name or app id

How to use it

List the published version history of an Android app on Aptoide by package name, numeric app id, or app URL. Each entry carries the version name and code, size, minimum SDK, hosting store, rating, malware scan result, and the direct APK download links (url, md5, sha1) for that specific version.

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, numeric Aptoide app id, or an Aptoide app URL (examples: "com.whatsapp", "75513329"; minLength: 1)
• count integer required — Max number of versions to return (min: 1)

Response

• @type string (default: "AptoideApp")
• id integer required
• name string required
• package string required
• alias string nullable
• size integer nullable
• image string nullable
• cover string nullable
• added_at string nullable
• modified_at string nullable
• updated_at string nullable
• description string nullable
• summary string nullable
• whats_new string nullable
• keywords array (default: [])
• screenshots array (default: [])
• videos array (default: [])
• web_url string nullable
• mobile_url string nullable
• download_count integer nullable
• play_download_count integer nullable
• age object nullable
  • @type string (default: "AptoideAppAge")
  • name string nullable
  • rating string nullable
  • pegi string nullable
• developer object nullable
  • @type string (default: "AptoideDeveloper")
  • id integer nullable
  • name string nullable
  • website string nullable
  • email string nullable
  • privacy_url string nullable
• store object nullable
  • @type string (default: "AptoideStore")
  • id integer nullable
  • name string required
  • image string nullable
  • description string nullable
  • badge string nullable
  • apps_count integer nullable
  • subscriber_count integer nullable
  • download_count integer nullable
  • review_count integer nullable
  • web_url string nullable
• file object nullable
  • @type string (default: "AptoideAppFile")
  • version_name string nullable
  • version_code integer nullable
  • md5 string nullable
  • size integer nullable
  • sha1 string nullable
  • signature_owner string nullable
  • min_sdk integer nullable
  • screen string nullable
  • gles integer nullable
  • abis array (default: [])
  • densities array (default: [])
  • malware_rank string nullable
  • download_url string nullable
  • download_url_alt string nullable
  • added_at string nullable
  • tags array (default: [])
  • used_features array (default: [])
  • used_permissions array (default: [])
• rating object nullable
  • @type string (default: "AptoideAppRating")
  • avg number nullable
  • count integer (default: 0)
  • votes array (default: [])
    • @type string (default: "AptoideRatingVote")
    • value integer required
    • count integer required
• play_rating object nullable
  • @type string (default: "AptoideAppRating")
  • avg number nullable
  • count integer (default: 0)
  • votes array (default: [])
    • @type string (default: "AptoideRatingVote")
    • value integer required
    • count integer required

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.