API, CLI & MCP

Send files from your code.

A file transfer API for the moment a script, a build or an AI agent needs to hand a big file to a real person: a documented REST API with webhooks, a command-line client, and an MCP server you connect with one sign-in.

Send a file freeSee pricing

Before

The build finished. Now what?

The export is 8 GB and the client needs it today. So someone babysits a browser tab, drags it into a website and pastes the link into an email — every single time.

With Yungle

One command, and a link comes back.

Send a folder from the terminal, a script or a CI job, and get a transfer link in return — with the same encryption, receipts and recipients as sending from the website.

How it works

Three steps. No manual.

  1. 1

    Sign in, or create a key

    The CLI and the MCP server sign you in through the browser. Scripts and CI use a key from your account settings.

  2. 2

    Send from anywhere

    Three REST calls and the bytes, or one command with the CLI.

  3. 3

    Hand over the link

    Email it to recipients straight from the call, or pass it on however your pipeline likes.

The details

Everything else worth knowing.

  • REST, documented

    A public OpenAPI 3.1 spec and docs at docs.yungle.co, readable without an account.

  • A real CLI

    Ship a folder from the terminal without keeping a browser tab open.

  • MCP, safe by default

    Your AI agent can look things up and share links. It never deletes or invites, and emails only with your yes.

  • Downloads are free

    Uploads include a monthly allowance and are metered after that. Downloads are never metered.

  • Receipts, by webhook

    A signed transfer.downloaded event when it is collected, or pull the events if your script has no public URL.

Worth knowing

  • A script without a public URL can pull the same events a webhook would push.
  • The vault and end-to-end encrypted transfers are not reachable through the API, the CLI or the MCP server — their keys never reach us.
  • API uploads include a free monthly allowance and are metered after that; downloads are never metered.

Questions, answered.

Ask us something else
Is the API available on the free tier?

Yes. Free accounts can create and send transfers, manage contacts and keep one webhook endpoint, through the API, the CLI and the MCP server. Collections need a paid plan.

Where is the documentation?

Everything is public at docs.yungle.co, with no account needed — authentication, uploads, transfers, collections, errors and limits, plus the OpenAPI spec.

Can my AI agent send files on my behalf?

It can share files as a link it hands back to you. Emailing them only happens if you allowed it when connecting, and then you confirm every send.

Can my server find out when a file is downloaded?

Yes. Register a webhook and Yungle posts a signed event when a transfer is ready, downloaded (once per visit), about to expire or expired, and when a file lands in a collection. No public URL? Pull the same events from the API instead.

Next featureTransfersSend up to 10 GB free, with no account and no ads. Uploads survive a dropped connection, and you see who downloaded your files and when.

Keep reading

Send your first file in ten seconds.

10 GB, free, right now — no account, no card, no ads. Pay us only when you want your work to stay put.

Send a file nowCreate an account
  • Cancel anytime
  • iDEAL, card or SEPA
  • Export or delete everything, yourself