An API for your program's files
Make an app, give it a key, and store files with it. What an app holds is kept apart from your own files and from your other apps, and counts toward the one allowance you already have.
Part of Pro, with 100,000 calls a month included, then 50 cents for each 100,000 beyond that, inside your spending limit. The prices
The first request
A key goes on every request. It is a password for the app: keep it on a server, never in a web page or in an app somebody can take apart.
curl -H "Authorization: Bearer ffk_live_..." https://api.filefreak.io/v1/filesWhat it gives you
Keys that can do less
A key is given some of 4 permissions (files:read, files:write, files:delete, usage:read) and can do nothing it was not given. It can be kept to one folder, which is then all it can see, and it can be given an end date. Revoking one stops it on its next request.
Uploads from a browser, without the key
Your server asks for upload addresses and hands them to your own page. Your user's browser sends the file straight to storage. The key never leaves your server, and a file of any size goes up in parts and carries on if it is interrupted.
Addresses that last
A file you make public has an address that does not expire. It stops working when you make the file private again, and not before.
Images at the size you ask for
Ask for a picture at 64, 128, 256, 512, 1024 pixels. Each size is made once and kept, so an avatar is not a photograph sent to every visitor.
Nothing made twice
Send an Idempotency-Key with a request that makes something. The same request sent again is given the first answer.
Limits you can see
One key may make 600 calls a minute. Every refusal is JSON with a short code that does not change. Each app can be given a ceiling of its own, so one runaway program cannot use up your account.
Every endpoint, every field
The reference is made by the API from the same definitions its requests are checked against, so it cannot describe something the API does not do. 14 endpoints.
Read the reference