mocop
Browse · Docs · Guide · Analyze

Yungle API

API by Yungle · rest

Send transfers, build collections and sync contacts from your own systems. Every account can use it: transfers and contacts on the free plan, collections on a paid one. Lists that can grow without bound (transfers, collection files) take limit and cursor and return nextCursor; pass it back unchanged for the next page, and stop when it is null. Any POST accepts an Idempotency-Key header (1–255 printable characters; a UUID). A retry with the same key and body within 24 hours replays the original success with Idempotent-Replayed: true and creates nothing. File bytes never travel through this API: endpoints that accept files return a tus endpoint and a per-file upload token, and you stream to that. See https://docs.yungle.co/guides/upload-large-files. The vault and end-to-end encrypted transfers are not reachable here, and cannot be: their keys are derived in the client and never sent to us. Errors are JSON with a stable error.code (the Error schema); error.docs…

Endpoint: https://yungle.co/api/v1

Verification: observed. Source: crawl.

Capabilities (48)

  • List collections
  • Create a collection
  • Collection detail
  • Rename or re-describe
  • Delete a collection and its contents
  • Download your own collection
  • List files
  • Register files for upload
  • Delete files
  • List folders
  • Create a folder
  • List guests
  • Invite guests by email
  • Remove a guest
  • List contacts
  • Create a contact
  • Get a contact
  • Replace a contact
  • Delete a contact
  • Follow a URL import
  • Download a link someone shared with you
  • The workspace plan and key behind this request
  • Your invite link and referral progress
  • List upload requests
  • Create an upload request
About · Contact · Privacy