Access codes on share links
A share link can now carry an access code. The person has to type it before the download starts, and we store the code only as a hash. Useful when the link travels further than you meant it to.
A share link can now carry an access code. The person has to type it before the download starts, and we store the code only as a hash. Useful when the link travels further than you meant it to.
Two things studios kept asking for. Deleted files now sit in a trash for seven days before they are really gone. And you can download your whole account as one zip with a manifest, any time, without asking us. Both are in the console and the API.
As announced in April, /api/v0 stopped serving today. It now returns 410 Gone with a short note pointing at /api/v1. If a script of yours just broke, that is why; swap v0 for v1 and it should work again. The error envelope and most paths are unchanged.
We rewrote the API and the new one lives under /api/v1. It has a single error envelope, proper status codes and a real OpenAPI document. The old /api/v0 keeps working for now but is frozen: no new features, and it will be switched off on 30 June. Move your tokens and scripts over; the paths are mostly the same with v1 in place of v0.
PATCH /api/v0/files/{id} now takes a new name or folder. Small, overdue, done.
You can now create a link to a file that expires on its own. Pick 1 hour, 1 day, 7 days or 30 days. We debated longer options and decided against them for now; a link that never dies is a link you forget about.