EasyDown REST API platform guide
Desktop, mobile status/detail, visitor, and t.cn links use the post workflow. Weibo video-show links with a 1034 object ID first use the public component endpoint and only enter the existing post fallbacks when component media is unavailable.
Use the EasyDown Weibo Media Download API to parse public posts, mobile status URLs, video-show links, and short links into complete video, image, gallery, and cover data.
Weibo video download API · Weibo image API
Production REST endpoint
POST https://api.easydown.org/api/v1/parseweibo.com/{uid}/{postId}m.weibo.cn/status/{id}m.weibo.cn/detail/{id}weibo.com/tv/show/1034:{objectId}h5.video.weibo.com/show/1034:{objectId}video.weibo.com/show?fid=1034:{objectId}t.cn/{code}mapp.api.weibo.cn/fx/...Share text containing a Weibo URLhttps://video.weibo.com/show?fid=1034:5324152400445628
curl -X POST https://api.easydown.org/api/v1/parse \
-H "Authorization: Bearer ed_live_xxx" \
-H "Content-Type: application/json" \
-d '{"url":"https://video.weibo.com/show?fid=1034:5324152400445628"}'The shared envelope stays stable while this platform determines which media arrays and attributes are populated.
Video posts and component video pages keep every available playback quality and cover. Image posts return every original image discovered in the target gallery.
{
"status": 200,
"data": {
"platform": "weibo",
"title": "Example weibo public post",
"thumbnail": "https://cdn.example.com/thumbnail.jpg",
"duration": 24,
"images": [
{
"url": "https://cdn.example.com/content-image.jpg",
"width": 1080,
"height": 1350
}
],
"videos": [
{
"url": "https://cdn.example.com/video.mp4",
"quality": "HD",
"mimeType": "video/mp4",
"width": 1080,
"height": 1920,
"hasAudio": true,
"source": "direct"
}
],
"audios": []
},
"msg": "success"
}The EasyDown website routes every Weibo media download through its proxy. REST clients should likewise use a backend proxy with a Weibo Referer, browser User-Agent, and forwarded Range header, then re-parse expired source URLs.
User-Agent: Mozilla/5.0
Referer: https://weibo.com/
Range: bytes=0-Profiles, personal video tabs, search pages, topics, super topics, articles, live pages, collections, private posts, and deleted posts are unsupported.
Only process public media you have the right to use. EasyDown does not bypass privacy controls, DRM, deleted content, or platform access restrictions.
Normalize t.cn links before caching a post identifier.
Choose a playback entry by quality metadata rather than relying on array order.
Re-parse image or video URLs after the source signature expires.
Create a private API token and allow this platform in its permissions.
POST one complete public post URL to the shared endpoint.
Select and proxy the required items from images, videos, and audios.
Use the MCP endpoint for AI agents, or open the browser tool for a manual public-media workflow.
Supported public single-post formats include weibo.com/{uid}/{postId}, m.weibo.cn/status/{id}, m.weibo.cn/detail/{id}, weibo.com/tv/show/1034:{objectId}, h5.video.weibo.com/show/1034:{objectId}, video.weibo.com/show?fid=1034:{objectId}, t.cn/{code}, mapp.api.weibo.cn/fx/..., Share text containing a Weibo URL. Profiles, personal video tabs, search pages, topics, super topics, articles, live pages, collections, private posts, and deleted posts are unsupported.
Video posts and component video pages keep every available playback quality and cover. Image posts return every original image discovered in the target gallery.
The EasyDown website routes every Weibo media download through its proxy. REST clients should likewise use a backend proxy with a Weibo Referer, browser User-Agent, and forwarded Range header, then re-parse expired source URLs.
A response containing at least one image, video, or audio URL costs 1 credit. Failed, unsupported, authentication, and empty-media results do not consume credits.