How to get a public URL for a video
Video files often arrive as form attachments, exports, or binary workflow data. Uploading them to FilePost gives your app a stable URL to save, pass to another service, or show to a recipient without building a storage bucket and delivery layer.
Use the same multipart endpoint for MP4, WebM, MOV, MKV, and other video files. The response includes the URL, file ID, size, and content type so the next system can decide whether to embed, download, or process the file.
Upload video files with FilePost
Use the authenticated FilePost upload API for video 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=@demo.mp4"
Example response
{
"url": "https://cdn.filepost.dev/file/…",
"file_id": "a1b2c3d4e5f6",
"name": "demo.mp4",
"size": 84210,
"content_type": "video/mp4"
}
What to do with the returned URL
Use the URL as the source for a video element, a download link, a CMS field, or the next automation step.
<video controls src="https://cdn.filepost.dev/file/…"></video>
Good uses for video to URL
- Video uploads from SaaS apps and forms
- Automation workflows that need a file URL
- Sharing or storing video exports behind one API
Know the boundary
FilePost does not transcode, compress, watermark, or create adaptive streaming renditions. Choose a video pipeline when codec conversion or streaming packaging is the main job.
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.