API Documentation
Complete reference for all downloader endpoints. Each endpoint consumes a different amount of credits per request.
Base URL
https://api.anysave.clickCredits per request
Cost varies by endpoint and platform. Rates are the same for all plans.
Which endpoint should I use?
All four endpoints download media — but each is optimized for a different scenario. Pick the one that fits your infrastructure and budget.
Cache Lookup
Instant · zero-credit
/downloader/cache/lookupChecks if a file was previously downloaded and cached in Telegram. Returns a ready-to-forward file_id — no download needed. Absolutely free — every request costs 0 credits. Returns 404 if the file has never been requested before.
Pros
- Free — 0 credits per request
- Instant response (milliseconds)
- Returns Telegram file_id for direct forwarding with custom inline keyboards
Cons
- Returns 404 if the file wasn't cached by anyone before
- Only useful for Telegram bots — file_id can't be used elsewhere
Use it if
You're building a Telegram bot and want the cheapest possible check before falling back to a real download.
Fast Links
Direct CDN · almost instant
/downloader/linksReturns direct CDN URLs from the source platform — no processing on our side. Best choice for the majority of use cases. Can return HLS streams, files of any size, or video without audio + separate audio track (never plain silent video). All file processing happens on your side.
Pros
- Cheapest download endpoint — near-instant response
- Works for any file size, HLS, DASH — no limits
- Preferred endpoint for most integrations
Cons
- You handle HLS merging, muxing video+audio, truncation on your side
- CDN links can expire — use them right away
Use it if
You have a capable client (browser, mobile app, or server) that can handle raw media files, HLS playlists, or merge video + audio tracks.
Sync Downloader
One connection · we do everything
/downloader/One HTTP connection kept open until the file is fully ready. Our server handles everything: truncates oversized files, merges HLS segments, muxes video with a separate audio track. Slow and heavy — only use it if your client can't process files itself. Costs more than Fast Links.
Pros
- Zero client-side processing — we deliver a finished file
- Automatic HLS merging, audio muxing, size truncation
- Single request, no polling
Cons
- Blocks a connection up to 5 minutes — heavy on both sides
- More expensive than Fast Links
Use it if
Your client is weak (low-power device, serverless function) and can't merge HLS or process large files. Consider our SDK instead — it does the same on top of Fast Links.
Async Tasks
Fire and poll · no blocking
/downloader/tasksSame power as Sync Downloader — same processing, same result — but non-blocking. Create a task, poll for status, download the file when ready. Perfect if you don't want to hold a long HTTP connection open. Also expensive; consider the SDK if you want the same behavior on top of Fast Links.
Pros
- No hanging connections — friendly to serverless and mobile
- Same processing as Sync (HLS merge, muxing, truncation)
- Result URL survives past the immediate request
Cons
- Same price tier as Sync Downloader
- Requires polling logic on the client
Use it if
You need heavy processing (4K, long HLS, large files) but can't afford to hold an HTTP connection open.