Skip to main content

Upload File from a URL to a Custom Folder endpoint – Supported URL Formats and Requirements

  • Apr 1, 2026 12:18 PM UTC
  • 0 replies
  • 15 views
  • Translate All

Here’s what Bob expects when using the “Upload File from a URL to a Custom Folder” endpoint, so you can avoid any surprises when sending requests.

 

This endpoint works by having Bob fetch the file from the URL you provide, so the format and accessibility of that URL really matter.

 

file:/// URLs aren’t supported 

These point to a local file system (like C:/Users/...), which Bob’s servers can’t access. The request will fail because there’s no way for Bob to reach files on a local machine.

 

The URL must be publicly accessible 

Bob needs to be able to reach the file over the internet. That means:

-No local paths
-No internal/private network URLs

-No authentication walls unless handled via signed URLs

 

Direct file links only 

The URL should point straight to the file itself (e.g., a .pdf, .docx, etc.), not a web page preview (like Google Drive preview links).

 

Signed URLs are supported

Temporary, secure links (like AWS S3 pre-signed URLs) work as long as:

-They are still valid at the time of the request

-They allow direct file download

 

HTTPS is expected (recommended standard) 

-https:// URLs are the standard and safest option

-http:// may work if publicly accessible, but it’s not recommended and may introduce issues (redirects, security restrictions, etc.)