/fdroid/apps/versions

POST /api/fdroid/apps/versions

Price: 5 credits

List version history of an F-Droid app by Android package name or app URL

How to use it

List the version history of an open-source Android app on F-Droid by its package name (or an F-Droid app URL), newest first. Each version returns its version name and code, added time, whether it is the suggested or a beta build, supported ABIs, minimum Android version, size, direct APK download and signature links, source tarball link, requested permissions, and changelog.

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 an F-Droid app URL (examples: "org.fdroid.fdroid", "com.termux", "https://f-droid.org/en/packages/org.fdroid.fdroid/"; minLength: 1)
• lang string — Locale for localized name, summary and description (default: "en")
• count integer required — Max number of versions to return (newest first) (min: 1)

Response

• @type string (default: "FdroidAppVersion")
• version_name string required
• version_code string nullable
• added_at integer nullable
• is_suggested boolean (default: false)
• is_beta boolean (default: false)
• min_android_version string nullable
• abis array (default: [])
• size string nullable
• download_url string nullable
• signature_url string nullable
• build_log_url string nullable
• source_url string nullable
• permissions array (default: [])
• whats_new 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.