every platform the API covers

directory

the nine platforms

Each page below is a reference, not a brochure: the exact request, the response fields, the credit cost, working code, and the cases where it will not work.

architecture

there are really only two request shapes

Six of the nine platforms go through a single universal endpoint. You pass a link and the API identifies the platform itself — which means adding a new one to your product is usually a validation change, not an integration.

# Instagram, TikTok, Pinterest, X, Facebook, RuTube — all the same call
curl "https://api.fastsaver.io/v1/fetch?url=<any supported link>" \
  -H "X-Api-Key: fs_sk_•••••••••••"

YouTube gets its own family of endpoints because it needs choices the others do not: which resolution, audio or video, search before download, and the Telegram file_id path for bots.

# YouTube — pick a format explicitly
curl -X POST https://api.fastsaver.io/v1/youtube/download \
  -H "X-Api-Key: fs_sk_•••••••••••" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://youtu.be/6dG1WWjew8s", "format": "audio"}'

Shazam is the exception to both: it takes an audio file rather than a link, and answers with a song identity instead of a download.

the contract

what every platform has in common

• The same X-Api-Key header. One key for everything.
• The same envelope: ok: true and a payload, or ok: false and a reason.
• A source field naming the platform, so one worker can handle every link type.
• Public content only. Private accounts, follower-gated posts and deleted media return an error, not a file.
• Signed download URLs that expire. Fetch the bytes in the same job rather than storing the link.
• Per-plan rate limits, from 10 requests per minute on Free to 900 on Mega.

When a platform changes its markup or its player — and one of them does, most months — the fix ships behind the endpoint. Your integration does not move.