How to upload a ZIP and get a URL
Archives are useful when several files need to travel together. FilePost gives the archive one stable URL, so an app or automation can deliver the bundle without exposing a storage bucket.
FilePost treats archives as files and preserves the bytes exactly as uploaded. That makes it a good delivery layer for generated bundles, exports, and handoffs where the consumer will unpack the archive itself.
Upload zip files with FilePost
Use the authenticated FilePost upload API for zip files. The endpoint returns a JSON object containing the public URL, file ID, size, content type, and filename mode.
curl -X POST https://upload.filepost.dev/v1/upload \
-H "X-API-Key: YOUR_API_KEY" \
-F "file=@export.zip"
Example response
{
"url": "https://cdn.filepost.dev/file/…",
"file_id": "a1b2c3d4e5f6",
"name": "export.zip",
"size": 84210,
"content_type": "application/zip"
}
What to do with the returned URL
Give the URL to a customer, release page, workflow step, or download client.
<a href="https://cdn.filepost.dev/file/…" download>Download archive</a>
Good uses for zip to URL
- Release and build artifact downloads
- Bundled customer exports
- Archive handoffs in automation workflows
Know the boundary
FilePost does not unpack, inspect, virus-scan, or selectively serve files inside an archive. Validate archives before upload when your security model requires it.
For the complete request and response contract, see the FilePost API documentation. You can also test the flow with the interactive upload on the homepage.