API docs for the file to URL workflow
A backend, worker, or automation step has the file. The docs show how to upload it, return the URL, control its lifetime, and handle failures.
- Reviewed by
- GetFileURL technical team
- Updated
- Create
- POST /v1/files
- Control
- expires_at and DELETE /v1/files/{file_id}
- Debug
- structured errors and visible response metadata
What this page answers
Start with the upload API, then read authentication and errors before wiring the request into live workflows.
- Reviewed by
- GetFileURL technical team
- Last updated
Read the small set of pages needed to ship a file URL handoff.
The API documentation is intentionally narrow. A working integration needs upload, authentication, lifecycle controls, and predictable errors.
Upload API
Request fields, response shape, multipart upload, expiry, and examples.
Authentication
How to send bearer keys, where to store credentials, and why browser-exposed upload keys need product policy before public use.
Expiry field
Store `expires_at` so public URLs do not become unmanaged storage.
Full v1 reference
Scan every OpenAPI-backed endpoint, response code, request body, and webhook receiver contract.
OpenAPI contract
Download the public OpenAPI YAML used for endpoint docs, SDK generation, and API-version registry metadata.
Connector starter kits
Review local Zapier and Pipedream draft actions without treating them as published marketplace connectors.
Document failure handling before users hit the first broken workflow.
Automation builders need errors and copyable examples as much as endpoint reference text. Those pages make the API easier to map in real tools.
Delete API
Use the returned file ID to remove public access after the destination system has fetched the file.
Errors
Expected auth, upload, size, type, expiry, and rate-limit failure shapes for workflow branches.
Code examples
Copy the same upload request into cURL, JavaScript, Python, or an HTTP automation node.
Common questions
Which API doc should I read first?
Start with the upload API, then read authentication and errors before wiring the request into live workflows.
Are lifecycle controls part of the API contract?
Yes. Expiry and deletion are core to the product because public file URLs should have a visible end state.
Do no-code tools use the same API?
Yes. Tools such as n8n, Make, Zapier, and Pipedream can use the same HTTP request shape when they can send multipart form data and parse JSON.