---
title: "FAQ — Credits, Limits & Platforms | FastSaverAPI"
url: https://fastsaverapi.com/faq/
description: "Answers about FastSaverAPI: supported platforms, credits and rate limits, the free tier, expiring download URLs, Telegram file_id and the domain change."
updated: 2026-08-10
api_base: https://api.fastsaver.io/v1
site_index: https://fastsaverapi.com/llms.txt
openapi: https://fastsaverapi.com/openapi.json
---

# frequently asked questions

The questions people actually ask before integrating: what FastSaverAPI covers, what a
request costs, what the limits really are, and where it deliberately stops. Endpoint-specific
questions live on each platform page .

## the basics

**Q: What is FastSaverAPI?**

A: A REST API that resolves a social-media link into a downloadable file plus its metadata. You send a URL and an API key over HTTPS; you get JSON containing a direct download URL, dimensions, duration and whatever else the platform exposes. It is infrastructure, not an app — there is no interface for end users, only endpoints for your code.

**Q: Which platforms are supported?**

A: Instagram, TikTok, YouTube, Pinterest, X (Twitter), Facebook and RuTube for media; Shazam for song recognition, charts and lyrics; and a Telegram-specific endpoint that returns a file_id for cached audio. The platforms page links to a reference for each.

**Q: Do I need cookies, proxies or a platform login?**

A: No, and that is most of the value. Residential proxies, rotating sessions, captcha walls and per-platform scrapers stay on our side of the API. Your side is one HTTPS request with one header.

**Q: Is there an SDK or a client library?**

A: No, deliberately. Every endpoint is a plain GET or POST with JSON, so requests , fetch , curl or your language's standard HTTP client is enough. A machine-readable description lives at /openapi.json if you want to generate a client.

## plans, credits and limits

**Q: What does the free tier include?**

A: 1,000 credits, no card, and access to every endpoint — nothing is gated behind a paid plan. The free tier is limited to 10 requests per minute. At 1.5 credits per Instagram or TikTok call that is roughly 660 downloads to evaluate with.

**Q: How do credits work?**

A: Each request spends credits based on how much work it takes. A TikTok fetch costs 1.5; a Shazam chart lookup costs 1; a 4K YouTube download costs 25. Plans come with a monthly credit allowance rather than a request quota, so cheap calls go further. GET /balance reports what you have left and costs nothing.

**Q: What are the rate limits?**

A: Per plan: 10 requests per minute on Free, 60 on Pro, 250 on Ultra and 900 on Mega. Exceeding it returns 429 . Custom plans go to 2000+ — ask if you need it.

**Q: Can I get a plan bigger than Mega?**

A: Yes. Custom credit limits from 5M upward, higher rate limits, dedicated infrastructure with an SLA and white-label arrangements are all available. Message support on Telegram and you will get a quote.

## technical questions

**Q: How long does a download_url stay valid?**

A: Not long. Most are signed URLs from the platform's own CDN and expire within hours; a YouTube download comes back as a one-shot transfer link on https://api.fastsaver.io/v1/tunnel that is minted for that job and does not outlive it. Fetch the bytes in the same job that made the call. Never store the URL and assume it will resolve tomorrow — store the source link and re-resolve it.

**Q: What is a Telegram file_id, and why does it matter?**

A: A file_id is a handle to a file already sitting on Telegram's servers. If your bot has one, it can send the file without ever downloading or uploading it — one API call and the user has the track. The alternative is fetching an MP3 to your server and re-uploading it, which costs bandwidth, adds seconds of latency and runs into Telegram's bot upload limits. See the Telegram bot page .

**Q: Can I download private or follower-only content?**

A: No. The API resolves publicly reachable content. Private accounts, follower-gated posts, close-friends stories and private groups return an error rather than a file, and that is not a limitation we intend to remove.

**Q: What happens when a platform changes something?**

A: We fix it behind the endpoint. That is the maintenance you are paying to avoid: your integration keeps calling the same path with the same parameters, and the breakage never reaches your code. Notable changes are posted to the Telegram channel .

**Q: Is using this legal?**

A: The API is a tool; what you do with the media it returns is your responsibility. Downloading content you own, content you have permission to use, or content for personal offline viewing is generally fine. Redistributing someone else's copyrighted work is not, and no API changes that. Check your jurisdiction and each platform's terms before you build a product on top of it.

## about the service

**Q: Why did the domain change, and is my key still valid?**

A: The API moved from fastsaverapi.com to api.fastsaver.io on 2026-07-24. Keys, endpoint paths and response shapes are unchanged — only the host. Old URLs are 301-redirected. The domain change notice has the full redirect map and a migration checklist.

**Q: Can an AI agent read this API without a human?**

A: Yes. /llms.txt is a machine-readable index of this site, /llms-full.txt carries the full text, and /openapi.json is an OpenAPI 3.1 description of the API with authentication, parameters and costs. Crawlers and assistants are explicitly allowed in robots.txt .

**Q: Where do I get support?**

A: Directly from the person who builds it, on Telegram: @coder2077 . There is no ticket queue. Announcements and incident notes go to @fastsaverapi .

## Keep reading

- Platform references — what each endpoint returns
- Guides — working code, end to end
- Domain change notice — fastsaverapi.com → api.fastsaver.io
- Current pricing — on api.fastsaver.io

## Still unsure? Test it for free

1,000 credits, no card, every endpoint unlocked. Or paste a link into the playground and read the JSON first.

Get a free API key
Open the playground
