Workspace
A workspace is one account’s space in Yungle: its transfers, collections, contacts, webhooks and storage. It has one owner, whose plan decides what the workspace can do and whose storage its files use.- Members are people the owner adds to the workspace. They work in it from the dashboard.
- Guests are people invited by email into a single collection. They see that collection and nothing else.
Transfer
A transfer is a set of files sent as one link that expires. It moves through these states:- Draft. You create the transfer and upload its files. Nothing is live and nobody is emailed. A draft that is never sent is deleted after 24 hours.
- Sent. You finalize it. The link at
urlstarts working, and any recipients you named are emailed it.finalizedAtis set andstatusisactive. - Expired or revoked. At
expiresAtthe link stops working and the files are deleted, andstatusbecomesexpired. Revoking does the same at once, andstatusbecomesremoved.
id; the slug in its link is a secret that lets anyone download.
Guide: Send a transfer.
Collection
A collection is a durable space for files, organized in folders (up to 10 levels deep), usually one per client or project. On a paid plan nothing in a collection expires. You share a collection through its secret link, or invite guests by email. Collections need a Leaf or Tree plan, with 250 GB or 1 TB of storage shared by all of a workspace’s collections. Guide: Client collections.Upload request
An upload request is a public page that lets anyone with its link upload files into one of your collections, without an account. You can add a password, an expiry and a checklist of what you expect. You can pause it and resume it, or close it for good. Each upload through it is a submission, and the request records who sent what. Guide: Receive files.Contact
A contact is an entry in the workspace’s address book: an email address, which is unique per workspace, with an optional name, company, phone number and type. Guide: Contacts.Files and scanning
Each file in a transfer or collection is uploaded with tus, a resumable protocol, or fetched by Yungle from a URL you give it. Once a file is uploaded, Yungle scans it for viruses. A file’sscanResult is null until the scan has run and clean after. An infected file is destroyed: its key is deleted, so it can never be downloaded.
Each file also carries a crc32 checksum, so you can check a download arrived intact.
Guides: Upload large files, Download files.
Encryption
Every file is always encrypted, each with its own key, which Yungle holds. Because Yungle holds the keys, it can scan files for viruses and show previews. Two features go further and are end-to-end encrypted: the files are encrypted on your device and the key never reaches Yungle.- End-to-end encrypted transfers. You opt in per transfer. The key travels in the
#part of the link, so such a transfer cannot be emailed by Yungle or password-protected. - The vault. A private collection encrypted with a key derived from your passphrase. The API cannot reach it.
Plans and metering
Yungle has a free plan and two paid plans, Leaf and Tree. The free plan covers transfers, contacts and webhooks; collections and upload requests need a paid plan. Uploads you make through the API are metered on their own, the same way on every plan: the first 10 GB each month are free, then €0.02 per GB from prepaid credit. Downloads are never metered. Limits lists the request and email limits; Pricing has the plans.Next steps
Quickstart
Send your first transfer.
Send a transfer
Everything a transfer can do.
Client collections
Folders, guests and durable storage for clients.
Authentication
Keys, scopes and the plan gate.
