Skip to main content
Add any publicly accessible video directly to a Cloudglue collection by passing its URL.

​
Add with the API/SDK

const result = await client.collections.addVideoByUrl({
  collectionId: 'my-collection-id',
  url: 'https://example.com/video.mp4',
  params: {},
});
The video will be added to Cloudglue and can be processed with full multimodal analysis (audio, visuals, and text). See Add Media to Collection for the full API reference.

​
Sync without a collection

To materialize a URL into a Cloudglue file without adding it to a collection, use Sync File from URL. The call is idempotent — syncing the same URL again returns the existing file. 
curl -X POST https://api.cloudglue.dev/v1/files/sync \
  -H "Authorization: Bearer $CLOUDGLUE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/video.mp4"}'
This accepts direct video URLs, public Dropbox share links, TikTok URLs, and Loom share URLs. YouTube URLs are not supported here — add those to a collection instead. Connector URIs (s3://, gdrive://file/<id>, …) sync through their data connector via Sync Data Connector File.

​
Supported URL types

Cloudglue supports several URL types:
  • Direct video URLs — any public URL pointing to a video file (e.g. https://example.com/video.mp4)
  • YouTube URLs — public YouTube video URLs (audio-only processing)
  • TikTok URLs — public TikTok video URLs (full multimodal)
  • Loom - public Loom share URLs (multimodal)
  • Dropbox file share links — www.dropbox.com/scl/fi/... links download anonymously when publicly accessible; login-gated links return a 403 (sync them through a Dropbox connector instead)
  • Data connector URIs — connector-specific URIs like gdrive://file/<id>, s3://<bucket>/<path>, etc.

​
URL types with special handling

  • Google Drive links (drive.google.com/file/d/...) resolve through your connected Google Drive connector — they are not anonymous downloads.
  • Video page links from Vimeo, OneDrive (1drv.ms, onedrive.live.com), and Box are not supported: these pages serve HTML, not video bytes, so they fail fast with a 400 naming the host. Provide a direct video file URL instead (known direct-download forms on those hosts, like app.box.com/shared/static/... or player.vimeo.com/progressive_redirect/..., still work).