The Transfer API moves external files into Convertly. Use it to fetch a public URL, store a ZIP archive as files, or import a folder from Google Drive, S3, or Dropbox.
For production workloads, prefer destination: "convertly-storage". Convertly can store the result, return signed download URLs, preserve extracted ZIP paths as folders, and keep large imports away from your app server.
Single-file URL transfers into Convertly Storage are asynchronous by default. The request creates a transfer job and returns 202 Accepted with a jobId; poll GET /api/jobs/{jobId} or subscribe to job updates to read the stored file result when it completes.
Public URL transfer
The response is queued:
When the job completes, GET /api/jobs/job_123 includes the stored file metadata and signed download URL in results.
destination: "download" returns the fetched file as the response body. destination: "convertly-storage" stores the file asynchronously by default. Set "async": false only for small request/response workflows where you explicitly want the API request to wait for storage.
ZIP transfer and extract
Set extract: true to download a ZIP archive, extract it, and save each entry into Convertly Storage.
Convertly creates a folder, preserves ZIP subfolders by default, stores each extracted file, and returns the stored file records.
Cloud folder import
Use cloudSource instead of sourceUrl to import files from a provider API.
Google Drive
Google Drive imports use the Google Drive account connected in the Convertly dashboard.
Use fileId instead of folderId to import a single Google Drive file.
S3 imports use request-scoped credentials. The credentials are used for the import request and are not stored.
Use key instead of prefix to import one S3 object.
Dropbox
Dropbox imports use a request-scoped Dropbox access token.
Request fields
Response
Queued storage transfers return a job envelope. Completed transfer jobs expose the stored file in the job results. Synchronous storage transfers, ZIP extraction, and cloud folder imports return stored file or folder metadata immediately.
Pricing
Transfer API usage counts against monthly processed transfer. Convertly meters source read plus destination write, so a 100 MB file stored in Convertly counts as about 200 MB of processed transfer. ZIP extraction counts the archive download plus extracted bytes written to storage.
Stored files count toward your HDAM storage quota. Storage overage is billed on monthly peak overage growth when enabled. Quotas and overage behavior: Limits and Limits → Media API.
Safety and scaling
Convertly blocks localhost, private-network, and non-HTTP source URLs. ZIP extraction rejects path traversal, skips directory entries, and enforces file-count and extracted-size limits.
Single-file URL-to-storage transfers run asynchronously. Poll the returned job until it completes, or use a webhook to receive the result.
Archive extraction and cloud imports run with bounded resources. Cloud imports process files sequentially and cap imports at 500 files per request. Last modified on July 31, 2026