WebFileTools API: automate your file processing
The WebFileTools API lets you automate file uploads and sharing from your scripts and applications.
Get an API key
- Create an account at /register
- Open /dashboard/api-keys
- Create a key with the upload scope
Key format: wft_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Authentication
Pass the key in the Authorization header:
Authorization: Bearer wft_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Quotas
| Plan | Calls / day |
|---|---|
| Free | 100 |
| Pro | Unlimited |
cURL example
curl -X POST https://webfiletools.com/api/upload \
-H "Authorization: Bearer wft_YOUR_KEY" \
-F "file=@document.pdf"
Python example
import requests
API_KEY = "wft_YOUR_KEY"
with open("document.pdf", "rb") as f:
r = requests.post(
"https://webfiletools.com/api/upload",
headers={"Authorization": f"Bearer {API_KEY}"},
files={"file": f},
)
print(r.json().get("url"))
JavaScript example
const fs = require("fs");
const FormData = require("form-data");
const API_KEY = "wft_YOUR_KEY";
const form = new FormData();
form.append("file", fs.createReadStream("document.pdf"));
const res = await fetch("https://webfiletools.com/api/upload", {
method: "POST",
headers: { Authorization: "Bearer " + API_KEY, ...form.getHeaders() },
body: form,
});
console.log((await res.json()).url);
Use cases
- Automated upload of daily exports (backup)
- CI/CD artifact publishing
- Zapier/Make/n8n workflows
- Batch invoice PDF processing
Security
- Never expose your API key in Git
- Use a different key per project
- Immediately revoke any compromised key from /dashboard/api-keys
Go further
- Full documentation: /api-docs
- Create an API key: /dashboard/api-keys