API docs for the file to URL workflow
Use these docs when a backend, worker, or automation step needs to upload a file and hand a direct public URL to another API.
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, Base64 input expectations, 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 API
Use `expires_in` and `expires_at` so public URLs do not become unmanaged storage.
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.
Answers before the workflow breaks
Which API doc should I read first?
Start with the upload API, then read authentication and errors before wiring the request into production 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.