What is a direct file URL?
A direct file URL is an HTTPS URL that returns the file bytes to a server-side fetch without requiring a browser session, permission prompt, or preview page.
- Reviewed by
- GetFileURL technical team
- Updated
- Direct URL
- Returns file bytes and useful headers
- Preview link
- Often returns HTML, redirects, or permission UI
- Workflow need
- Server-side fetch by OCR, AI, social, document, or webhook APIs
What this page answers
No. A share link often opens an app page. A direct file URL returns the file bytes and headers to a server-side fetch.
- Reviewed by
- GetFileURL technical team
- Last updated
A direct file URL resolves to the actual file.
If an API asks for a file URL, it usually means the API will fetch that URL from its own servers. The URL must work without your login session.
Returns bytes
The response body is the file itself, not an HTML share page or application shell.
Keeps headers
Content type, size, and disposition help the destination decide how to process the file.
Has lifecycle
For workflow files, the URL should expire or be deleted after the job finishes.
Links that open in your browser can still fail for APIs.
A user-visible link can depend on cookies, redirects, app permissions, or a preview route. Server-side APIs do not share that context.
Google Drive preview links
They may show a document viewer or permission page instead of serving bytes directly.
App attachment URLs
They can expire quickly or require the app session that created them.
Redirecting links
Some destination APIs refuse redirects or fetch the final page with the wrong headers.
Upload the file to a URL layer built for machine handoffs.
GetFileURL accepts the workflow file, returns a direct public CDN URL, and includes lifecycle fields so the URL does not become unmanaged storage.
Upload the actual file
Send the file bytes from your app, worker, script, or automation HTTP step.
Pass response.url onward
Map the returned URL to the destination API field that asks for a file URL.
Store file_id
Use the file ID to delete the URL after processing or support cleanup later.
Common questions
Is a direct file URL the same as a share link?
No. A share link often opens an app page. A direct file URL returns the file bytes and headers to a server-side fetch.
Why do APIs reject Google Drive or Airtable links?
Those links can require permissions, redirect through preview pages, or expire before an external server fetches the file.
Should direct file URLs be permanent?
Not for most workflow handoffs. Use expiry or deletion so public access ends after the downstream job finishes.