EasyDown REST API platform guide
EasyDown matches the requested shortcode in the upstream result instead of assuming the first returned item is correct, then exposes the complete post media through the shared REST schema.
Use the EasyDown Threads Download API to parse public media posts and receive every video variant, carousel image, content image, and cover returned for the target shortcode.
Threads video download API · Threads media API
Production REST endpoint
POST https://api.easydown.org/api/v1/parsethreads.com/@user/post/{shortcode}threads.net/@user/post/{shortcode}Optional query string or /media suffixhttps://www.threads.com/@eekeai/post/DDhV3LWhrlk
curl -X POST https://api.easydown.org/api/v1/parse \
-H "Authorization: Bearer ed_live_xxx" \
-H "Content-Type: application/json" \
-d '{"url":"https://www.threads.com/@eekeai/post/DDhV3LWhrlk"}'The shared envelope stays stable while this platform determines which media arrays and attributes are populated.
Media posts can return every valid video version and each image in a carousel. Duplicate source variants may remain when they represent separate upstream candidates.
{
"status": 200,
"data": {
"platform": "threads",
"title": "Example threads 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"
}Use a backend proxy with a browser User-Agent and the matching Threads origin as Referer. Store returned media URLs only briefly because source signatures and variants can change.
User-Agent: Mozilla/5.0
Referer: https://www.threads.net/
Range: bytes=0-Text-only posts, profiles, feeds, replies, search results, private posts, and deleted posts return no downloadable media.
Only process public media you have the right to use. EasyDown does not bypass privacy controls, DRM, deleted content, or platform access restrictions.
Use the canonical post shortcode URL, including threads.com or threads.net.
Treat text-only success responses as no-media results.
Keep every returned carousel image instead of selecting only the first item.
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 threads.com/@user/post/{shortcode}, threads.net/@user/post/{shortcode}, Optional query string or /media suffix. Text-only posts, profiles, feeds, replies, search results, private posts, and deleted posts return no downloadable media.
Media posts can return every valid video version and each image in a carousel. Duplicate source variants may remain when they represent separate upstream candidates.
Use a backend proxy with a browser User-Agent and the matching Threads origin as Referer. Store returned media URLs only briefly because source signatures and variants can change.
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.