Endpoint Data Sources

The endpoints that hand you back actual media bytes — Download Media and the deprecated Scrape Media — first check whether we already have that file in our own CDN.

• If we have it cached → you get a URL on our own cdn.fansapi.com. Download Media returns a 302 redirect to it (most HTTP clients follow redirects automatically; curl needs -L). Scrape Media returns it as temporary_url in the response body. No credits are charged in this case, because OnlyFans is never contacted.
• If we don't have it cached yet → Download Media returns a 302 redirect to dl.fansapi.com, which streams the bytes from OnlyFans. We also queue a background cache download. Once caching completes, later requests can be served from our CDN.

Non-DRM downloads support Range and HEAD requests. Range downloads are billed for the bytes streamed; HEAD returns metadata without a body, download credits, or a background cache download. DRM downloads use a separate endpoint and do not support Range or HEAD.

Download Media from the Fansly CDN always answers with a 302 redirect — it never streams bytes through us. Where it points depends on whether the file is cached:

• If we have it cached → a 302 to a signed cdn.fansapi.com URL, valid for 1 hour. Fansly is never contacted.
• If we don't have it cached yet → a 302 to the original signed cdn*.fansly.com URL, so your download starts immediately, and we queue a background job to save our own copy. The next call for that same file gets the cdn.fansapi.com redirect instead.

Because it is always a redirect, your HTTP client must follow redirects (curl needs -L).

Streaming manifests (.m3u8 and .mpd) are redirected but never cached — a manifest is a playlist of separately-signed segment URLs rather than a media file, so a cached copy would be useless.

Any endpoint that returns OnlyFans CDN URLs in its response body — List Chat Messages, List Posts, List Vault Media, and so on — follows the same caching pattern, applied per-URL:

• Each https://cdn*.onlyfans.com/* URL in the response is checked against our CDN.
• URLs we already have cached are replaced with the equivalent https://cdn.fansapi.com/* URL before the response is returned to you.
• URLs we don't have cached yet are left as the original https://cdn*.onlyfans.com/* URL, and we start saving our own copy. Future responses that include the same URL will return the cdn.fansapi.com version instead.

This rewriting is applied per-URL, so a single response can contain any mix of OnlyFans CDN URLs and rewritten cdn.fansapi.com URLs depending on what we've already cached.

These Fansly endpoints rewrite https://cdn*.fansly.com/* URLs in their response body:

• URLs we already have cached are replaced with a signed https://cdn.fansapi.com/* URL, valid for 15 minutes.
• URLs we don't have cached yet are passed through untouched, as the original signed cdn*.fansly.com URL.

Rewriting is per-URL, so a single response can mix both kinds. Treat every media URL as opaque and download it promptly either way — both the raw Fansly URLs and our rewritten ones expire.