← Yungle

Changelog

/api/v1 is additive-only. New fields and endpoints may appear here; nothing existing will change meaning, disappear, or become required. Anything that would break a client ships as /api/v2, and v1 keeps working.

What counts as additive

  • A new endpoint, or a new method on an existing one.
  • A new optional request field.
  • A new field in a response — so parse leniently and ignore what you do not recognise.
  • A new error code, within an existing status. Branch on codes you know and treat the rest by status.
  • A new scope. Existing keys keep exactly the scopes they were issued.

What will not happen without a version bump: removing or renaming a field, changing a field's type, making an optional field required, changing the status code for an existing condition, or narrowing what a scope grants.

2026-07-29 — v1

First release.

  • API keys, created in Settings → API keys. Six scopes across transfers, collections and contacts.
  • Transfers: create as draft, add and remove files, finalize, amend expiry and download limits, revoke, and read download receipts.
  • Collections: create, rename, delete, register and delete files, create and list folders, invite and remove guests.
  • Contacts: full CRUD.
  • Uploads via tus, resumable at part granularity, on the same endpoint the web app uses.
  • An OpenAPI 3.1 document at /api/v1/openapi.json, generated from the same definitions the server validates with.