title: Help description: Short answers to common Velravio questions: uploading, sharing, access codes, quotas, trash, export, API tokens and deleting an account.
Help¶
Short answers to common questions. For anything not here, use the contact form. Use your browser's find (Ctrl+F) or the search box at the top.
Files¶
How do I upload a file?
Drag it into the workspace, or use the API: PUT /api/v1/files?name=<name> with the bytes as the body. Both return the size and SHA-256.
Why was my upload rejected?
A single file must be 50 MB or smaller, and your account holds up to 200 MB in the beta. Over either limit, the upload is refused with a clear message.
How do I check a file is intact?
Every file shows its SHA-256. After downloading, run sha256sum and compare. The download also sends a Digest header with the same hash.
I deleted a file by mistake.
Deleted files sit in the trash for 7 days. Open the trash in the workspace and restore it.
Sharing¶
How long do share links last?
Choose 1 hour, 1 day, 7 days or 30 days when you create the link. It expires on its own and is then removed.
Can I protect a link with a code?
Yes. Add an access code when you create the link. The person types it before the download starts. We store the code only as a hash.
Account¶
Can I change my zone?
No. A zone is fixed to the account. Export your files as a zip and sign up again in the other zone.
I forgot my password.
We do not send reset emails. Write through the contact form from the email on the account and we will help you reset it. If you are signed in, change it in the console.
How do I get all my files out?
Use export in the console, or GET /api/v1/export. You get one zip with every file and a manifest.csv.
How do I delete my account?
In the console, confirm with your password. This removes the account and every file in it from the zone and cannot be undone.
API¶
How do I get an API token?
Create one in the console. The secret is shown once; store it then. Use it as Authorization: Bearer <token>.
Do API requests need a CSRF token?
Only cookie-session requests that change state need X-CSRF-Token. Bearer-token requests do not.