Media URLs
This guide explains the different types of URLs you can use for the mediaUrl parameter in the Redner B2B API.
Overview
The mediaUrl parameter accepts different types of URLs depending on your use case:
- HTTP/HTTPS URLs - Direct links to publicly accessible files
- URLs from Upload Mechanism - For private files or better control
HTTP/HTTPS URLs (Direct Download)
Provide a direct link to your media file:
https://example.com/video.mp4
https://cdn.example.com/audio.mp3
https://storage.example.com/files/presentation.mp4
Supported Formats
Video: mp4, webm, ogg
Audio: mp3, wav, m4a, flac, amr
Subtitles: srt (for Translate and Voice-Over APIs)
Requirements
- URL must be publicly accessible (or include authentication in URL)
- Must use HTTP or HTTPS protocol
- File must have a valid extension
- Maximum file size: 3500 MB
Not Supported
- localhost or private IP addresses (192.168.x.x, 10.x.x.x, 172.16-31.x.x)
- FTP, SFTP, or other protocols
- URLs without file extensions
- YouTube, Vimeo, or other streaming platform URLs
Example
json
{
"mediaUrl": "https://example.com/video.mp4",
"sourceLanguage": "en-US"
}URLs from Upload Mechanism
For files uploaded via the upload API, you'll receive an S3 URL:
s3://bucket-name/path/to/file.mp4
These URLs are automatically generated when you use the upload mechanism and can be used directly in API requests.
Upload Mechanism (For Large Files)
For files larger than 1 GB or private files, we recommend using the upload mechanism:
- Initialize upload:
POST /v1/upload/init - Upload file: Use the presigned URL
- Confirm upload:
POST /v1/upload/confirm
See the Upload Guide for complete details on the upload process.
Common Errors
| Error | Cause | Solution |
|---|---|---|
| "Invalid URL format" | URL doesn't start with http:// or https:// | Check URL protocol |
| "File not found" | URL returns 404 | Verify URL is accessible |
| "Download timed out" | File too large or slow network | Use upload mechanism instead |
| "Unsupported format" | Invalid file extension | Use supported format |
| "File too large" | File exceeds 3500 MB | Use upload mechanism |
| "URLs to local networks not allowed" | URL points to private IP | Use public URL or upload mechanism |
Best Practices
When to Use Direct URLs
- Files are already hosted and publicly accessible
- File size is under 1 GB
- You want the simplest integration (single API call)
- You don't mind the API downloading from your server
When to Use Upload Mechanism
- Files are private or not publicly accessible
- File size is over 1 GB
- You need better error handling and retry logic
- You want faster processing (no download time)
Next Steps
- Learn about the Upload Guide for detailed upload instructions
- Explore the API Reference for endpoint documentation
- Set up Webhooks to receive job completion notifications