All-in-One Social Media Downloader API
Version 1.0.0 | Last Updated: September 13, 2025
The All-in-One Social Media Downloader API is a robust solution for extracting media content from multiple social media platforms through a single, unified API. This service allows developers to easily implement media downloading capabilities into their applications without the need to handle individual platform integrations.
All API requests require authentication using an API key. Your API key should be included with every request to the API endpoints.
To obtain an API key, please contact our administrator via Telegram: @Alifur Rahman Jonayed. API keys are provided based on your usage requirements.
Include your API key as a query parameter in your requests:
The API provides a single endpoint that handles all platforms through automatic detection.
This endpoint automatically detects the platform from the provided URL and returns downloadable links.
The API accepts the following query parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
key |
string | Required | Your API key for authentication |
url |
string | Required | The URL of the media you want to download |
All API responses are returned in JSON format. Successful responses have the following structure:
Boolean
Indicates whether the request was successful or not.
String
The current version of the API.
Integer
Unix timestamp of when the response was generated.
Object
Information about the API developer.
String
The detected platform from the URL (e.g., "youtube", "tiktok", etc.).
Object
Platform-specific data containing the downloadable media links and metadata.
The data object contains different properties depending on the platform:
| Platform | Available Fields |
|---|---|
| YouTube | title, thumb, video, video_hd, audio, quality, channel |
| TikTok | title, thumb, video, video_no_watermark, audio, author |
title, thumb, media (array), author |
|
title, thumb, video, video_hd, author |
|
title, thumb, video, video_hd, author |
|
| Terabox | title, size, file, type |
| Likee | title, thumb, video, video_no_watermark, author |
When an error occurs, the API will return a JSON response with success: false and details about the error:
The API uses standard HTTP status codes to indicate the success or failure of a request:
| HTTP Code | Error Code | Description |
|---|---|---|
200 |
- | Success - The request was successful |
400 |
MISSING_PARAMS |
Missing required parameters (key or url) |
400 |
INVALID_URL |
The provided URL is invalid or not supported |
403 |
INVALID_KEY |
The API key is invalid or not found |
403 |
KEY_EXPIRED |
The API key has expired |
429 |
RATE_LIMIT |
Rate limit exceeded for this API key |
500 |
SERVER_ERROR |
Internal server error |
502 |
PLATFORM_ERROR |
Error fetching data from the target platform |
success property in the response to determine if the request was successful.
To ensure fair usage and service stability, API requests are subject to rate limiting. Rate limits vary based on your API key tier:
| Tier | Requests per Minute | Requests per Hour | Requests per Day |
|---|---|---|---|
| Basic | 30 | 300 | 1,000 |
| Premium | 60 | 1,000 | 10,000 |
| Enterprise | 200 | 5,000 | 100,000 |
If you exceed your rate limit, the API will return a 429 Too Many Requests status code. For applications requiring higher limits, please contact us for custom plans.
Below are examples of how to integrate the API in different programming languages:
The API currently supports the following platforms:
Supports videos, shorts, and playlists. Returns multiple quality options and audio extraction.
Supports videos with and without watermark. Returns video and audio streams.
Supports posts, reels, and stories. Returns all available media from carousel posts.
Supports tweets with videos and GIFs. Returns HD and SD quality options.
Supports videos from posts, reels, and stories. Returns HD and SD quality options.
Supports file downloads from Terabox cloud storage.
Supports videos with and without watermark.
Always check the success property in the API response. If it's false, the error object will contain details about what went wrong. Implement proper error handling in your application to provide meaningful feedback to your users.
No, the API can only download publicly available content. Private, age-restricted, or geographically restricted content cannot be accessed by the API.
Implement a caching mechanism in your application to store API responses for previously requested URLs. Consider using Redis, Memcached, or even a simple database to store responses. Set an appropriate TTL (time-to-live) for cache entries (e.g., 24 hours) to ensure your users get fresh content when needed.
If you receive a 429 error, implement an exponential backoff strategy before retrying. If you consistently hit rate limits, consider upgrading your API plan or optimizing your application to reduce unnecessary calls.
Download URLs provided by the API are typically valid for 24-48 hours, depending on the platform. For optimal user experience, we recommend downloading the media as soon as possible after receiving the API response or implementing a system to refresh URLs if needed.