Answers: how much storage am I using? how much is left? what plan am I on? what can this connection do? Returns the workspace, its plan and quota, and the key's permissions.

Answers: what have I sent recently? what is expiring soon? which deliveries has nobody picked up? who did I send that to? Returns recent transfers with size, recipients, download count, expiry date and share link.

Answers: what is in this transfer? was it delivered? has a specific recipient downloaded it? is it safe to share? Returns the files with their malware-scan verdicts, plus per-recipient delivery and download status for one transfer id.

Answers: did the client download it? when? how many times? Returns download events with timestamps and per-recipient status. One visit can fetch several files: events that share a sessionId belong to the same visit.

Answers: what collections do I have? which are empty? how big is each one? Returns collections with file counts, sizes and when each was last touched. A collection is a durable space clients are invited into, as opposed to a one-off transfer. Never includes the vault, which is unreadable to this server by design.

Answers: what is the link for this collection? how much is in it? when does it expire? Returns one collection with its secret share link, file count, total size and expiry.

Answers: what files are in this collection? what is in this folder? are the raws uploaded yet? Returns filenames, sizes and types. Omit folderId for every file; pass "root" for the top level only, or a folder id. Filenames only — never file contents.

Answers: how is this collection organised? what folders exist? Returns the folder tree. Ordered by depth, then path (not a pre-order traversal). Each folder carries its parentId and its full path.

Answers: who has access to this collection? who did I invite? has someone accepted? Returns the invited guests and their status. Guests are not workspace members — they can view and download this one collection and nothing else.

Answers: what is this client's email address? who do I have saved? Returns the workspace address book. A contact grants no access on its own — it is a convenience, not a permission.

Answers: which upload links do I have out? has anyone sent files through them? Returns each public upload page that feeds a collection, with its link, status and how much has arrived.

Answers: who has uploaded through this link, when, and how much? Returns the request and its submissions, newest first, with the name, email and note each uploader typed.

Answers: what is in this link someone sent me? how do I get these files? Turns a Yungle link (https://yungle.co/t/… or /c/…), or one of your own transfers or collections, into signed download URLs: one per file, with its folder path, plus a ZIP. The URLs need no key, support HTTP Range (resumable), and work for 24 hours — fetch them with curl or any HTTP client. Resolving someone else's link counts as one download of it, like opening it in a browser.

Save the files of a Yungle link, or of one of your own transfers or collections, into a folder on this machine — resumably, keeping their folder structure. Files land in a new subfolder of directory; nothing outside it is written, and files already there at full size are skipped. Returns the saved paths.

Prepare a draft transfer for files that live on a machine with a shell, and return one upload command per file. Each command (npx -y yungle-cli put …) needs no Yungle key: it carries a token that can write only that file, for two hours, and it resumes if interrupted. Nothing is shared and nobody is emailed until the transfer is finalized.