One HTTP call turns a generated HTML report or a zipped site into a hosted page with its own URL. Works from n8n, Zapier, Make, Pipedream, or plain curl.
Any supported file works. Code: HTML · ZIP · JSON · JSONL · YAML · TOML · XML · SQL · MD · INI · ENV · PROPERTIES · LOG · WASM
No SDK and no configuration. POST a file to the upload endpoint with your API key and read the finished URL out of the JSON response. Any language or tool that can send an HTTP request can use it.
# One call: POST the file, read back the live URLcurl -X POST https://upload.tf/api/v1/upload \ -H "x-api-key: $UPLOADTF_KEY" \ -F "file=@report.html" \ -F "name=weekly-report"Response
{
"success": true,
"data": {
"url": "https://weekly-report.upload.tf",
"slug": "weekly-report",
"hasHtml": true
}
}Sign in, open the dashboard, and create a key. API access is included with paid plans, and your key works immediately.
Point your workflow's HTTP step at the upload endpoint, attach the file as form data, and send your key in the x-api-key header.
The response carries the live URL. Pass it to the next step: post it to Slack, save it to a sheet, or email it to a client.
The file your automation just produced goes straight to a URL, with nobody dragging files into a browser at 2 a.m.
Every upload gets its own https address on your subdomain. It opens in any browser, with no login wall in front of your recipient.
Send a PUT with the same name and the page updates at the same URL, so a weekly report keeps one permanent link.
The upload endpoint accepts an HTML page or a ZIP of a static site and publishes it at its own URL. It is built for the reports, dashboards, and pages your workflow generates. Other file types work today through the browser uploader on this page.
No. Any tool that can send a multipart HTTP request works: n8n's HTTP Request node, Zapier's Webhooks action, Make's HTTP module, a Pipedream code step, or curl in a shell script.
Create an API key in your dashboard and send it in the x-api-key header, or as a Bearer token if your tool prefers an Authorization header. Keys never go in the URL.
The API is included with paid plans, which also raise size limits and keep links live longer. You can try everything manually first with the free uploader on this page, no account needed.
Yes. Give the upload a name and it publishes at that subdomain; send a PUT to the same name and the content is replaced while the URL stays the same. That makes recurring jobs idempotent.
Building on n8n? Or shipping Zaps? See uploading from Zapier.
