The short version
| Yungle | |
|---|---|
| Public API | Documented, versioned, OpenAPI 3.1 spec. Reads free, writes on a paid plan. |
| Command-line client | Yes — resumable, survives an interrupted upload. |
| AI assistant access | An MCP server, read-only by design. |
| Where files live | One server in Germany. Backups in the EU. |
| Encryption | Every file encrypted at rest with its own key. |
| Free tier | 5 GB per transfer, 7 days, no account needed. |
| Paid | From €5/month for 100 GB and 90-day retention. |
Deliberately not a feature-by-feature table against a named competitor. Their pricing and capabilities change, a comparison written today would be wrong within months, and you can read their site as well as we can. What is stated above is what Yungle does, which is the part we can keep true.
What the API actually gives you
Delivery becomes a step in a pipeline rather than a website someone visits. Three calls and the bytes:
# Create a draft — nothing is live and nobody is emailed yet
curl -X POST https://yungle.co/api/v1/transfers \
-H "Authorization: Bearer $YUNGLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"files":[{"name":"final.mov","size":8123456789}]}'
# …stream the bytes to the returned tusEndpoint…
# Send it
curl -X POST https://yungle.co/api/v1/transfers/$ID/finalize \
-H "Authorization: Bearer $YUNGLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"recipients":["client@example.com"]}'Then read who collected it, so your own project tool can tell you rather than you checking.
Where Yungle is the wrong choice
Stated plainly, because finding out later is worse:
- It runs on one server. There is no global CDN, so a download from Australia crosses the world. That is the trade for knowing exactly where your files are.
- It is small. No enterprise SSO, no SLA, no procurement paperwork, and support is one person.
- There are no webhooks yet, so integrations poll.
- No mobile apps. The site works on a phone; there is nothing to install.
- If your files must not be readable by the host at all, the ordinary product is not that — it encrypts per file with keys Yungle holds, which is what makes previews and virus scanning possible. The vault and end-to-end transfers are the opt-in exceptions, and they are the parts the API cannot reach.
Start reading for free
Reading the API is free on any account — list transfers, read download receipts, browse collections. Creating and sending come with a paid plan.