yungle
Python client for Yungle: private, EU-hosted file transfer, a WeTransfer alternative with an API. Send files of any size as an expiring link, build collections for clients, keep contacts in sync.
pip install yungle
export YUNGLE_API_KEY=yk_live_…
from yungle import Yungle
yungle = Yungle()
sent = yungle.send(["render.mov", "notes.pdf"], to=["client@example.com"], message="Final cut")
print(sent["url"])
send creates a draft, uploads each file resumably, and sends it. With no to it only
returns a link. Every account can use the API: transfers and contacts on the free plan,
collections on a paid one. The first 10 GB of API uploads each month are free.
- Every endpoint is a method:
list_transfers,transfer_downloads,create_collection,add_collection_files,create_contact, … Responses are the API's JSON as dicts. Reference: https://docs.yungle.co/api-reference - Pages are followed for you by
all_transfers()andall_collection_files(id). - Retries are safe. Throttles and server errors are retried with backoff, and every
POST carries an
Idempotency-Key, so a retried create never makes a second copy. - Errors raise
YungleError; branch onerr.code. - Uploads go through
upload_file(tus_endpoint, target, path), a small tus client that resumes from the server's last committed part and renews its two-hour token as it runs. - Imports:
yungle.send(urls=["https://…/render.mov"])has Yungle fetch files that are already online, so they never pass through your process. - Downloads:
yungle.download("https://yungle.co/t/…", "incoming/")saves a shared link (or links fromtransfer_download_links/collection_download_links) resumably, keeping folders and verifying each file's CRC-32. - Upload requests:
create_request(collection_id, title)makes a public upload page;list_requests,get_request,set_request_statusmanage them.
Webhooks. Check a delivery against the raw request body before trusting it:
from yungle import verify_webhook
if not verify_webhook(request.body, request.headers["Yungle-Signature"], secret):
return HttpResponse(status=400)
Source and issues: https://github.com/heindewilde/yungle-clients. MIT.
Metadata
Release files for yungle 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| yungle-0.2.0.tar.gz | 26.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| yungle-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.6 kB
Release files / yungle-0.2.0.tar.gz
| Download URL | yungle-0.2.0.tar.gz |
|---|---|
| Size | 26.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d2f4de8b3e69e7a0cfe8008fd3c1c18dded7e436f697d6ec6a485eb530be578
|
|
BLAKE2b-256 checksum How to use checksums |
f24f8bdefec5c96081aefa8ffc85d3664d63efd95edb7f294a0ffadb2f5159dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 11, 2026.
Transparency logRelease files / yungle-0.2.0-py3-none-any.whl
| Download URL | yungle-0.2.0-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aeb712c9b80dffa94cdbb63e85af66f276fb0b1143e23d9c532f15f355d3e11e
|
|
BLAKE2b-256 checksum How to use checksums |
eb546e7058a23b842b90e2324fa2283ea25bee26756fc6764056d51b69f9299c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 11, 2026.
Transparency log