Docs for turning files into API-ready URLs
Start with the upload API, then add expiry and delete controls so every workflow-generated file has a clear lifecycle.
- Reviewed by
- GetFileURL technical team
- Updated
- Upload
- POST /v1/files
- Expiry
- returned expires_at
- Delete
- DELETE /v1/files/{file_id}
What this page answers
Start with the upload API reference, then add expiry and delete behavior once the URL handoff is working.
- Reviewed by
- GetFileURL technical team
- Last updated
Copyable docs for the first file URL workflow.
The docs are organized around what a builder needs to ship: create a URL, control how long it works, and remove it when the workflow is done.
Upload API
Endpoint, authentication, multipart request shape, response fields, and structured errors.
Expiry field
How returned `expires_at` makes public URL retention visible.
Delete API
How to use the returned file ID to remove public access after a workflow completes.
Use docs with utility and workflow pages, not in isolation.
SEO pages explain the user problem. Docs give builders the implementation detail needed to solve it.
File to URL
The broad utility page for users searching how to upload a file and get a link.
Image to URL
Image-specific handling for AI, OCR, social, CMS, and generated media workflows.
PDF to URL
Document-specific handling for invoices, reports, contracts, and OCR workflows.
Common questions
Where should I start?
Start with the upload API reference, then add expiry and delete behavior once the URL handoff is working.
Are these docs for developers only?
No. They also map cleanly to n8n HTTP Request nodes, Make HTTP modules, Pipedream steps, and Zapier webhook actions.
Do docs include final pricing limits?
No. Public plan limits should be added only when product limits are final and enforced by the API.