justapk
Download any APK by package name. 6 sources, automatic fallback, zero config.
justapk download org.telegram.messenger
One command. Six sources. Always gets the APK.
Why?
Existing APK downloaders break constantly — sites add Cloudflare, change APIs, go offline. justapk doesn't care. It cycles through 6 sources automatically until one works. Under the hood it uses reverse-engineered mobile APIs and Cloudflare bypass via TLS fingerprint impersonation.
Install
pip install justapk
Python 3.11+
Usage
download — grab an APK
justapk download <package> # auto-select best source
justapk download <package> -s apkpure # from a specific source
justapk download <package> -v 11.6.2 # specific version
justapk download <package> -o ./apks/ # custom output directory
justapk download <package> --no-convert # keep XAPK as-is (no merge)
search — find apps
justapk search telegram
justapk search telegram -s fdroid
info — app metadata
justapk info org.telegram.messenger
justapk info org.telegram.messenger -s apkpure
convert — XAPK/split APK to single APK
justapk convert app.xapk
justapk convert app.xapk -o output/
Merges split APKs (base + native libs + assets) and signs with a debug key.
sources — list available sources
justapk sources
All commands output JSON to stdout. Progress goes to stderr — pipe-friendly by design.
Sources
Tried in this order. If one fails, the next one picks up automatically.
| Source | How it works | Notes | |
|---|---|---|---|
| 1 | APK20 | REST API + HTML parsing | No Cloudflare |
| 2 | F-Droid | JSON API | FOSS apps only (~4K packages) |
| 3 | APKPure | Reverse-engineered mobile API | Largest catalog |
| 4 | APKMirror | HTML scraping + curl_cffi |
Cloudflare bypass |
| 5 | Uptodown | Reverse-engineered mobile API | No Cloudflare |
| 6 | APKCombo | HTML scraping + curl_cffi |
Cloudflare bypass |
Python API
from pathlib import Path
from justapk import APKDownloader
dl = APKDownloader()
# Download with auto-fallback
result = dl.download("org.telegram.messenger", output_dir=Path("./apks/"))
print(result.path, result.size, result.sha256)
# Search across all sources
apps = dl.search("telegram")
for app in apps:
print(app.package, app.name, app.source)
# Get app info
info = dl.info("org.telegram.messenger")
if info:
print(info.name, info.version)
# Pin a specific source
result = dl.download("org.telegram.messenger", source="apkpure")
License
Metadata
Release files for justapk 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| justapk-0.1.1.tar.gz | 17.3 kB | With provenance | Details for justapk-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| justapk-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for justapk-0.1.1-py3-none-any.whl |
Total release size: 42.1 kB
Release files / justapk-0.1.1.tar.gz
| Download URL | justapk-0.1.1.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4654e8d72c70a40cb89a494a5500ac087617bdcceae11750f15ec17ce5aab3e
|
|
BLAKE2b-256 checksum How to use checksums |
5db9a7a3ca1ade1e389dc670b33553bca4b63e5970a7ba01e6bcc2acc8c53816
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency logRelease files / justapk-0.1.1-py3-none-any.whl
| Download URL | justapk-0.1.1-py3-none-any.whl |
|---|---|
| Size | 24.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dce8cbe9b885381b44e98ada364f8995cf2572887076102d1f4d5e06545e5c78
|
|
BLAKE2b-256 checksum How to use checksums |
ff9dc772b76ad7e561b38d6c3b33271d64a52c1c1b2172d529d4d7c6da265fc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency logSecurity for justapk 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for justapk-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.