# Fansly API > The complete Fansly API platform. 200+ live endpoints, real-time HMAC-signed webhooks, native n8n / Zapier / Make.com integrations. Built for agencies running multiple creators, professional creators backing up archives, and developers building Fansly-powered tools. Fansly API is an independent platform that provides a programmatic interface for connecting Fansly creator accounts to external tools. We are not affiliated with Fansly.com or Fenix International Limited. The platform is operated by Fans Holdings OÜ, an EU entity (VAT EE102827084), with engineering based in Prague. We have been in production for over five years with zero accounts banned across 5,000+ connected accounts, processing 150M+ API requests and webhooks for 500+ companies. --- ## Key facts - Operating in production for 5+ years - Zero accounts banned across 5,000+ connected Fansly creator accounts - 150M+ API requests and webhooks processed - 500+ companies using the platform - 220K+ developer and operations hours saved - 99.98% uptime over the last 90 days - 200+ live API endpoints across accounts, fans, messages, media, posts, vaults, polls, earnings, stories, statistics - HMAC-SHA256 signed webhooks on every event type (messages, sales, subscriptions, renewals, tips, post interactions) - Native integrations: n8n (the only Fansly API with one), Zapier, Make.com - Self-serve and dedicated engineering teams - Free tier available — 10 credits, no credit card required --- ## Features - **Complete Fansly API** — 200+ live endpoints covering accounts, messaging, media, fans, earnings, posts, vaults, and polls. - **Full Account Authentication** — Email, password, and 2FA login support. Connect real Fansly creator accounts without browser automation. - **API Keys & Permissions** — Fine-grained scopes per key. Create, rotate, and revoke instantly. Built for multi-team agencies. - **Live API Playground** — Run any of 200+ Fansly endpoints in your browser. Inspect responses before writing code. - **Real-Time API Logs** — Every request logged with payload, status, and latency. Diagnose issues without leaving the dashboard. - **Captcha Bypass & Proxy** — Automatic captcha handling and rotating proxy infrastructure. Reliable access at production scale. - **24/7 Engineer Support** — Talk to an engineer, not a chatbot. Telegram, email, and in-app — answered around the clock. - **Always-On Endpoint Updates** — Fansly changes their internal API constantly. We ship compatibility fixes within hours, not weeks. - **Fansly Webhooks** — HMAC-signed webhooks fire on every message, sale, renewal, subscription, and tip event. Real-time, no polling. --- ## Automation - **Native n8n, Zapier & Make.com** — Three first-party integrations. The only Fansly API with a native n8n node. No reverse-engineering, no proxies, no headless browsers — just stable nodes that hit live endpoints. - **Ready-to-Run Fansly Templates** — Pre-built automations for whale alerts, mass DMs, churn re-engagement, and revenue exports. Import a template, paste your API key, run in minutes. - **No-Code Fansly Data Export** — Download fans, messages, earnings, or content to CSV in one click. No SQL, no code, no engineering ticket — point, click, export. --- ## Custom development use cases - **Multi-creator reporting dashboards** — Roll up revenue and fan activity across every creator on your roster. Built for the questions your finance team and account managers actually ask. - **End-to-end Fansly automation** — Mass DM workflows, churn winback systems, PPV launch sequences, whale-tip alerts. Connect to Slack, n8n, your CRM — production-grade reliability. - **Custom Fansly stack integrations** — Connect Fansly to your CRM (HubSpot, Pipedrive, Salesforce), BI tools (BigQuery, Snowflake, Looker), or in-house systems. Bespoke endpoints when off-the-shelf does not fit. --- ## What customers say > "We always had terrible experiences with developers… but not with Fansly API. They allowed us to build a customer software solution for referral tracking connections for our acquisition agency. Whenever something needed a quick fix, update or support it was fast and reliable." > — Lukas, Fansly Marketplace, FancyModels.vip > "Integrating FanslyAPI was a game-changer — it cut our development time from 6 months down to just one week. Super intuitive, reliable, and exactly what we needed to move fast." > — Nicolai L., Fansly superapp, Hello Butter > "Fansly API made building our search engine a smooth and easy process. The tool is simple to navigate, pricing is fair, and the support is great at answering questions & fixing issues when they arise." > — Shane Carroll Francis, Deeplinks that increase sales, Juicy Bio > "The team is fantastic to work with—white glove from start to finish. They built a bespoke, real-time dashboard tailored to our agency, and their deep knowledge of the Fansly platform made the entire process seamless and impactful." > — Andrew E., 8 figure OFM Agency --- ## Pricing Plans from $69/month (Basic) and $299/month (Pro, 5 accounts). Free tier with 10 credits, no credit card required. Enterprise dynamic pricing as low as $11.60/account at scale. ### Free — Free Test the full Fansly API — 200+ live endpoints, no-code integrations, 10 credits to validate any workflow before you commit. - Accounts: 1 - RPM: 1,000 - Credits: 10 - Support: Email, Telegram & WhatsApp - Included: 1 Account, 1,000 RPM, 10 Credits, Access to Over 200+ Endpoints, No Code Module, No Code Data Export, Support, Public Profile Searching ### Basic — $69/month $69/month for solo creators, indie developers, and anyone running 1-2 connected Fansly accounts. Webhooks included. - Accounts: 2 - RPM: 1,000 - Credits: 30,000 Free Monthly Credits - Support: Email & Telegram - Included: 1 Account, 1,000 RPM, 30,000 Free Monthly Credits, Access to Over 200+ Endpoints, No Code Module, No Code Data Export, Webhooks, Dedicated Mobile Proxy Infrastructure, Advanced Link Tracking, Support, Public Profile Searching ### Pro — $299/month $299/month for agencies running 5+ creator accounts. Advanced analytics, custom API development, and priority support. - Accounts: 5 included - RPM: 5,000 - Credits: 100,000 Free Monthly Credits included + 10,000 per additional account - Support: Email, Telegram & WhatsApp - Included: 5 Accounts Included, 5,000 RPM, 100,000 Free Monthly Credits, Access to Over 200+ Endpoints, No Code Module, No Code Data Export, Webhooks, Dedicated Mobile Proxy Infrastructure, Advanced Link Tracking, Advanced Analytics, Custom API Development, Early Access to Premium Endpoints, Priority Support, Public Profile Searching ### Enterprise — Get Quote Custom infrastructure for 100+ account operations. Dedicated engineering team, private endpoints, scaled proxy and RPM allocations, technical account manager. - Accounts: Custom — based on your needs - RPM: Custom — optimized for your scale - Credits: Custom — based on integration depth - Support: Dedicated Account Manager + Engineering Support - Included: Custom-Built Systems, Custom Integrations & Endpoints, Infrastructure Scaling, Dedicated Technical Account Manager, Consulting & Architecture, Priority Feature Requests, Recommended from 100+ accounts ### Pro volume discounts (per additional account) - +20 accounts: 10% OFF — $26.1/account - +50 accounts: 20% OFF — $23.2/account - +100 accounts: 30% OFF — $20.3/account - +200 accounts: 40% OFF — $17.4/account - +300 accounts: 50% OFF — $14.5/account - +500 accounts: 60% OFF — $11.6/account - +1000 accounts: Custom — get in touch/account --- # Feature pages --- # The team operating Fansly API Fansly API is operated by an experienced engineering team. Before launching Fansly API, the same group shipped the OnlyFans API and the FansMetrics platform, successfully acquired in 2023. Today the infrastructure powers 5,000+ Fansly connected creator accounts. ## Company timeline ### 2021 — FansMetrics Launched 🥇 #1 OnlyFans Search Engine ### 2023 — Successfully Acquired FansMetrics acquisition completed ### 2024 — OnlyFans API Launched The API agencies asked for ### 2025 — Fansly API Launched Now powering Fansly too ## By the numbers - 150M+ — API Requests & Webhooks - 500+ — Companies using Fansly API - 220K+ — Developers/Operations hours saved ## Key facts - Operating in production for 5+ years - Zero accounts banned across 5,000+ connected Fansly creator accounts - 150M+ API requests and webhooks processed - 500+ companies using the platform - 220K+ developer and operations hours saved - 99.98% uptime over the last 90 days - 200+ live API endpoints across accounts, fans, messages, media, posts, vaults, polls, earnings, stories, statistics - HMAC-SHA256 signed webhooks on every event type (messages, sales, subscriptions, renewals, tips, post interactions) - Native integrations: n8n (the only Fansly API with one), Zapier, Make.com - Self-serve and dedicated engineering teams - Free tier available — 10 credits, no credit card required View on fansly-api.com: https://www.fansly-api.com/about-us --- # Custom Fansly API integrations Most agencies hit the same wall around 10 creators: native Fansly tools cap out, public APIs miss key endpoints, engineering hires take months. Our team builds the custom pieces — CRMs, dashboards, bespoke endpoints — on top of the same Fansly API powering 500+ companies. Production-ready in 2-6 weeks. ## Use cases ### Multi-creator reporting dashboards Roll up revenue and fan activity across every creator on your roster. Built for the questions your finance team and account managers actually ask. - Real-time metrics - Revenue & Performance analytics - Fan & Creator analytics - Cross-creator reporting ### End-to-end Fansly automation Mass DM workflows, churn winback systems, PPV launch sequences, whale-tip alerts. Connect to Slack, n8n, your CRM — production-grade reliability. - Message automation - Fan segmentation - Content scheduling - Whale Alert Systems ### Custom Fansly stack integrations Connect Fansly to your CRM (HubSpot, Pipedrive, Salesforce), BI tools (BigQuery, Snowflake, Looker), or in-house systems. Bespoke endpoints when off-the-shelf does not fit. - CRM integration - Payment processing - Data synchronization - Custom webhooks View on fansly-api.com: https://www.fansly-api.com/custom-development --- # Fansly Downloader: Export Every Data Type from Fansly Download your Fansly media, messages, fans, transactions, and tracking links from a web dashboard or via API. Built for agencies managing 20+ creators, professional creators backing up their archives, and developers building Fansly tools. No Chrome extension. No HAR files. No browser scraping. No bans. ## What you can export The most complete Fansly data export tool on the market. Designed for large agencies, professional creators, and developers who need accuracy, speed, and scale. ### Public Profiles Scrape and export public Fansly creator profiles with powerful filters for pricing, activity, location, and media count. ### Media & Posts Download all Fansly images, videos, PPV content, and posts in one click. Preserve data for backups, analysis, or AI training. ### Links & Campaigns Export Fansly tracking links and campaign data to measure traffic, conversions, and revenue performance across promotions. ### Transactions Export full Fansly transaction history including subscriptions, tips, PPV purchases, and message earnings in clean formats. ### Banking & Payouts Download detailed Fansly payout and transfer history for accounting, tax reporting, and financial analysis. ### Fans & Subscriptions Scrape and export fan and subscription data to analyze renewals, churn, engagement, and subscriber lifetime value. ### Messages Export complete Fansly chat history including paid messages and media, ready for analytics or custom AI assistants. ### API & Automation Automate Fansly scraping and data exports with a powerful API built for multi-account workflows and scheduled syncs ## Use cases For creators, agencies, and devs — use it as a no-code download tool or automated scraper via API. ### Agency Model Acquisition Agencies use it to scale model scouting and outreach — scraping Fansly, Instagram, Twitter, and TikTok profiles that match top-earning, active creators. Filter by GEO, engagement, and activity to build email funnels. ### Creator Discovery Site Build a creator discovery site with searchable creator profiles, filters, leaderboards, and trending pages powered by continuously refreshed public profile data and API automation. ### AI & LoRA Training Automatically download Fansly images, videos, and chat messages at scale to train private LLMs or LoRA models using clean, structured, and reliable datasets. ### Financial Insights Scrape and export Fansly transactions, payouts, and earnings data to Excel or BI tools for fast, reliable financial reporting and insights. ### Platform Migration Fast exports or automated API pulls to move your Fansly data anywhere, including images, videos, messages, fans, and transactions. ### Backups & Ownership Keep complete local backups of all Fansly content, media, and messages with automated or on-demand exports for full data ownership. ### Agency Reporting Export multi-account Fansly data in a single workflow to build client dashboards, reports, and consolidated analytics effortlessly. ### Content Optimization Analyze Fansly media performance and pricing data to identify which content types convert best and optimize your posting strategy. ## Frequently asked questions ### How do I download all my Fansly data? Sign up free, connect your Fansly account in the dashboard, click Export, pick what you want (media, messages, fans, transactions), choose a date range, and download. CSV for tabular data, ZIP for media. No Chrome extension, no HAR file workflow, no browser scraping. ### Is it legal to download Fansly data? Yes — your own data. You retain rights to your account history and content. The Fansly Downloader gives you tools to export YOUR account: your media, your messages, your fan list, your earnings. It does not enable downloading other creators' private content. ### Will using the Fansly Downloader get my account banned? No. We have run for 5+ years with zero account bans across 5,000+ connected accounts. Unlike scrapers that simulate browser activity, we connect through authenticated API sessions — the same protocol the official Fansly app uses. ### Do I need a Chrome extension to download Fansly data? No. The Fansly Downloader runs entirely in a web dashboard. No extension to install, no browser permissions to grant, no detection risk from extension fingerprinting. Just sign in and export. ### What file formats does the Fansly Downloader support? Media exports as ZIP preserving original photo and video quality. Tabular data (transactions, fans, messages) exports as CSV ready for Excel, Google Sheets, BigQuery, or accounting software. Developers can pull JSON via the REST API. ### Can I download Fansly messages and chat history? Yes. Export every chat message including paid PPV media, regular DMs, mass messages, and fan-side replies. Each export includes full metadata: timestamps, fan IDs, payment status, attached media URLs. ### Can agencies download data from multiple Fansly accounts at once? Yes — that is the primary use case. Connect every creator account to one Fansly Downloader workspace, then export across the roster in a single workflow. Per-creator and consolidated exports both supported. ### How long does a full Fansly export take? Small exports (1,000 transactions, ~100 photos) complete in under a minute. Large exports (10,000+ messages, full media archive) take 5-30 minutes depending on volume. Exports run async — you receive an email when ready. View on fansly-api.com: https://www.fansly-api.com/fansly-downloader --- # Run Fansly operations without a single line of code Replace 30-40 hours/week of manual DM scheduling, revenue exports, and fan tracking with workflows in n8n, Zapier, or Make.com. Setup takes 5 minutes. Native Fansly node in every n8n instance — no install, no permissions, no engineer required. ## Features ### Reconcile revenue without spreadsheet hell Per-fan, per-link, per-campaign revenue exports to Sheets or BigQuery. Month-end takes minutes, not afternoons. ### Catch every whale tip in real time Webhook on tip.received fires a Slack or Telegram alert to your chatter. Re-engage while the fan is still in the chat — not next morning. ### Schedule a week of DMs in 30 minutes Sunday-night planning session replaces daily chatter logins across 20 creator accounts. Saved-for-Later API queues a full week of mass messages. ### Push Fansly data wherever your team works Airtable, Sheets, Notion, Slack, HubSpot, BigQuery, Snowflake — pipe Fansly data into whatever stack you already use. ### 5 years, 5,000+ accounts, zero bans Native 2FA support (SMS, Authenticator, Face ID), rotating mobile proxy infrastructure, encrypted vault. Built to survive Fansly UI changes without breaking your workflows. ### Talk to an engineer in under 30 minutes Telegram, email, in-dashboard chat. Real engineers on the other end — not first-line ticket triage. ## Ship your first Fansly automation in under 5 minutes Free tier — 10 credits to test any workflow, no credit card required. Most agencies have working automation before lunch. View on fansly-api.com: https://www.fansly-api.com/no-code --- # Fansly API vs APIFansly: 200+ Endpoints Built Over 5 Years vs 35 Shipped in 12 Days They cloned our copy. They cannot clone five years of production infrastructure, 5,000+ connected accounts, and zero bans. Here is how the two platforms actually compare. ## They Document 62 Endpoints. Only 35 Work. | Feature | Fansly API | APIFansly | | --- | --- | --- | | Live API Endpoints | 200+ production-tested endpoints | 35 live endpoints (27 are planned/404) | | Track Record | 5+ years, zero bans, 5,000+ accounts | 12 days old, zero public customers | | Webhooks | Rich events: messages, sales, renewals, subscriptions | Messages only, Pro plan required ($129/mo) | | No-Code Automation | Native Make.com, n8n, and Zapier | Make.com only — n8n and Zapier "coming soon" | | AI Analytics Suite | Chat, fan, financial analytics with AI intelligence | No AI analytics of any kind | | Data Export | One-click export of everything | No data export tool | | API Playground | In-browser testing for every endpoint | No playground | | Team Management | Members, roles, and granular permissions | No team features | | Status Page & Uptime | Public status page, 99.98% verified uptime | No status page, unverifiable uptime | | Money-Back Guarantee | 60-day money-back guarantee | No guarantee mentioned | ## 8 Things We Ship That APIFansly Cannot Offer Not roadmap promises. Capabilities live in production right now, verified against their public docs and endpoints. ### 200+ Endpoints, Every One Live and Documented Auth, messaging, media, fans, earnings, posts, vaults, webhooks, and more. APIFansly documents 62 but only 35 resolve. The other 27 return 404 or sit behind a "planned" label. ### Webhooks That Cover More Than Messages Sales, renewals, subscriptions, tips, all pushed to your endpoint in real time with HMAC-signed payloads. APIFansly delivers message events only, locked behind their $129/mo Pro tier. ### n8n, Zapier, and Make.com — All Three, Today Official nodes and native modules across every major no-code platform. APIFansly supports Make.com alone; n8n and Zapier are listed as "coming soon" with no shipping date. ### AI That Predicts Churn Before Revenue Drops Whale detection, churn scoring, fan profiling, chat performance analysis, and revenue forecasting. All powered by machine learning on your live data. APIFansly has zero AI features. ### Full Data Export — Your Information, Your Machine Messages, transactions, fan records, media file. Download everything in one click. APIFansly provides no bulk export tool. Data that goes in does not come out. ### An API Playground to Test Before You Build Run any endpoint live in your browser. Inspect request shapes, response payloads, and error codes. APIFansly has no interactive testing environment. ### Five Years of Zero-Ban Operations 5,000+ connected accounts. Not one banned. Public status page with 99.98% verified uptime. APIFansly launched 12 days ago with zero public customers and no operational history. ## Frequently asked questions ### APIFansly is cheaper — why would I pay more? Surface-level, yes: $129/mo vs $299/mo at Pro tier. But APIFansly Pro gives you 35 working endpoints, message-only webhooks, and Make.com as the sole no-code option. Our Pro includes 200+ live endpoints, rich webhooks on every event type, native n8n + Zapier + Make, AI analytics, one-click data export, and volume discounts up to 60% off. At 20 accounts, our per-account cost drops to $26. They have no volume pricing at all. ### APIFansly claims 62 endpoints — how is that different from your 200+? They document 62, but only 35 resolve to a working API. The remaining 27 are listed as "planned" or return 404 errors. Their changelog has not shipped an update since March 2. Our 200+ endpoints are live, tested, and have been in production for over five years across 5,000+ connected accounts. ### Is my account safe connecting to any third-party API? This is the right question. We have operated for 5+ years with zero accounts banned across 5,000+ connections. We maintain a public status page with 99.98% verified uptime. APIFansly launched approximately March 1, 2026. They have zero public customers, zero testimonials, and no operational track record to evaluate. ### What if I need webhooks on a lower plan? Our Basic plan at $69/mo includes webhooks for messages, sales, renewals, and subscriptions — all HMAC-signed. APIFansly locks webhooks to their Pro plan at $129/mo, and even then only delivers message events. If you need real-time notifications without paying for Pro, that option does not exist on their platform. ### Does Fansly API cover the Fansly platform specifically? Yes. Fansly API covers the full Fansly surface: accounts, messaging, media, fans, earnings, posts, vaults, polls, and more — 200+ live endpoints. APIFansly targets Fansly too, but ships with 35 working endpoints, message-only webhooks, and no AI analytics or no-code coverage beyond Make.com. ### APIFansly has a free plan with 30 credits. Can I test there first? You can, but 30 credits is roughly a handful of API calls — barely enough to test authentication. We also offer a free tier with 10 credits, but the real comparison happens at production scale. Sign up for both free plans, run the same workflow on each, and see which one actually handles your use case. ### Who is behind APIFansly? APIFansly operates under ABSKOOP LTD (UK company #15562577), owned by Abdelkodouss Belhaimer. Their privacy policy states they are "not formally incorporated," which contradicts the UK entity filing. Their Terms of Service reference "Moroccan Law" despite the UK jurisdiction. The blog lists "Mark Lucas" as the author — a different name from the registered owner. These inconsistencies are worth considering when entrusting creator account credentials. ### What if APIFansly catches up on features? Possible, but building production-grade infrastructure takes years, not weeks. We spent 5+ years shipping 200+ endpoints, an AI analytics suite, three no-code integrations, team management, data exports, and a playground. Catching up requires engineering depth, operational experience, and customer trust — none of which appear overnight. View on fansly-api.com: https://www.fansly-api.com/comparison/apifansly --- # Fansly AI Fan Analytics: spot every whale before they churn. 10% of fans drive 80% of revenue — Fan Analytics surfaces them in seconds. The subscriber CRM that flags whales, predicts churn, and shows what every fan actually spent across every creator on your roster. Built on the #1 Fansly API. ## Features Every signal a chatter needs to personalize, every metric a manager needs to forecast, and every alert an owner needs to protect revenue — wired to live Fansly data, filterable by creator and date. ### Fan Overview Dashboard Total subscribers, paying fans, free followers, renewals, new signups, returners, at-risk — one screen, filterable by creator and date. Replaces six spreadsheet tabs and a Monday-morning Slack thread. ### Smart Filtering & Search Slice fans by lifetime value, subscription date, PPV history, tip totals, stream attendance, or refund flags. Surface your top 50 whales — or your 100 most-likely churners — in under five seconds. ### Fan Detail Deep Dive Click any fan: LTV, subscription timeline, messages per day, PPV purchases, tip history, biggest single transaction, full activity log. The intel sheet your chatter wanted before sending the next reply. ### AI Fan Summary Auto-extracts names, kinks, hobbies, content requests, travel plans, anniversaries, fears, fantasies, favorites — from chat history. Turns 4,000 messages into a 200-word persona your team can actually act on. ### Whale Alerts & Churn Triggers Real-time pings when a $500+ tipper engages, when a high-LTV fan stops opening DMs, or when a top spender misses renewal. Set thresholds once and never miss a save — or a closer-grade opportunity. ### Team Notes & Handoffs Internal notes on every fan profile. The next chatter on shift inherits the full context — last gift, kink preferences, payment quirks, no-go topics — without a Slack thread or a 'who has the doc?' ## Use cases From the chatter on shift at 3 a.m. to the owner reviewing the quarter, every layer of your operation uses fan data differently. Six workflows that pay for the subscription on their own. ### Churn Prevention At-risk detection flags fans who paid last cycle but skipped renewal. Your team gets a 48-hour window to re-engage with a targeted offer — most agencies see this list a month too late, after the fan has already moved on. ### Whale Identification Rank fans by lifetime spend and 30-day tip velocity. Set whale alerts so the second a $200 PPV buyer hits the inbox, your top closer takes the conversation — not the new hire on rotation. The right voice on the right whale. ### Personalization From Chat History AI reads every message and surfaces the personal details that move fans from 'buyer' to 'regular': pet names, fantasies, content gaps, anniversaries. Chatters open with context — not 'hey bb' — and conversion follows. ### Cross-Sell & Upsell Intelligence See exactly what each fan has bought — PPV posts, customs, paid messages, tips — and what they haven't. Promote the format they have never tried. Untapped revenue, named and queueable for the next mass. ### Reactivation Campaigns Identify fans who churned 30, 60, or 90 days ago alongside their previous spending pattern. Run win-back campaigns aimed at the cohort most likely to convert — usually 8x cheaper than acquisition, with warmer intent. ### Multi-Creator Roster Reporting Filter analytics across the full roster or drill into one account. Compare retention rate, average LTV, and churn velocity creator-by-creator. Find the patterns top performers share — and replicate them across the rest. ## Frequently asked questions ### What is Fansly Fan Analytics? Fansly Fan Analytics is an AI-powered subscriber CRM for Fansly agencies and solo creators. It consolidates every subscriber on every creator account — lifetime value, purchase history, churn risk, message volume, tip totals — into one filterable view so your team can identify whales, prevent churn, and personalize chat at scale. ### Can Fan Analytics predict which Fansly subscribers will churn? Yes. The at-risk model flags fans who paid in the last subscription cycle but did not renew, plus fans whose engagement (message frequency, PPV opens, tip cadence) has dropped below their historical baseline. Your team sees the list within hours of the signal — not weeks after the fan is gone. ### How does whale detection work for Fansly creators? Fans are ranked by lifetime spend, 30-day tip velocity, and PPV purchase rate. You can set custom whale thresholds (e.g. lifetime spend over $1,000, single tip over $500) and receive real-time alerts when a fan crosses the line — so your highest-converting chatter takes the conversation, not the new hire. ### Does Fan Analytics work across multiple Fansly creator accounts? Yes — this is the primary agency use case. Connect every creator account on your roster to one workspace. Filter analytics across the full roster, compare creators side by side, or drill into a single account. Retention rate, average LTV, and churn velocity all roll up to the agency level. ### How is this different from the native Fansly analytics dashboard? Native Fansly analytics show top-line numbers per creator: total earnings, subscribers, message volume. Fan Analytics works at the subscriber level — every fan, every purchase, every churn signal — and crosses creators in one view. It is the difference between a P&L summary and a customer database. ### Where does the AI fan summary data come from? The AI reads each subscriber's chat history with the creator and extracts structured details — names, kinks, hobbies, content requests, travel plans, anniversaries, fears, fantasies, favorites. It runs against your own connected data only. Nothing is shared, sold, or used to train external models. ### Is Fansly Fan Analytics free? Yes, there is a free tier with 10 credits to test the workflow on one creator. Paid plans unlock multi-creator workspaces, higher API quota, and longer historical data retention. See the pricing page for current tiers. ### Will connecting my Fansly account get it banned? No. We have operated for 5+ years with zero account bans across 5,000+ connected accounts. We connect through authenticated API sessions — the same protocol the official Fansly app uses — not through browser scraping or extension fingerprinting. View on fansly-api.com: https://www.fansly-api.com/ai-fan-analytics --- # Fansly AI Fan Summaries: close the month before lunch. Eleven tabs, three spreadsheets, and somebody’s memory is not a Fansly reporting system. AI Fan Summaries consolidates earnings, trends, and period comparisons across every creator on your roster — filterable by account and date, ready before your AM stand-up starts. ## Features Pick a creator or your full Fansly roster, set a date range, and the dashboard does the math. No CSV exports, no copy-paste into Slides, no waiting for the data team. ### Multi-Creator Selector One account, a pod of five, or the full 60-creator roster. Every metric, chart, and table snaps to the scope you picked. Solo creator check-ins and quarterly board reviews use the same screen — no extra exports. ### Custom Date-Range Controls Last 7 days, a specific calendar month, a launch week, a promotion cycle. The date picker shapes itself to your operating calendar — not the other way around. Built for how agencies run, not how dashboards are wired. ### Full Earnings Breakdown Subscriptions, posts, messages, tips, streams — every revenue category separated and summed. Plus account count, message volume, and media output. The exact line items your finance lead asks for, in the order they ask for them. ### Historical Performance Timeline 3, 6, or 12 months of Fansly earnings (subscriptions, posts, tips, streams) plotted as a single trend. Inflection points jump off the page. A flat decline reads as a flat decline — not 30 rows in a CSV nobody opens past line 6. ### Period-vs-Period Comparison Stack two windows side by side. Absolute delta and percent shift across every line. Answer "what changed and by how much" in five seconds, not five minutes — and not after the executive review has already moved on. ### Rapid-Scan Filters Toggle between revenue categories without leaving the page. Surface the signal, skip the noise. Built for operators answering questions mid-call — not analysts running ad-hoc queries the day after. ## API endpoints Three endpoints power the core summary workflow: aggregated earnings overviews, time-series history, and structured period comparisons. Production-ready and fully documented. ### Earnings Overview Pull total earnings and category-level breakdowns - subscriptions, posts, messages, tips, streams and content stats for any combination of accounts. ### Historical Performance Return monthly aggregated revenue data across a configurable time range. Feed the numbers straight into trend charts to spot inflection points early. ### Period Comparison Compare two time periods and get back summary totals, category breakdowns, and chart-ready data showing exactly what changed and by how much. ## Use cases Whether you manage 5 accounts or 200, AI Fan Summaries plugs into the workflows you already run — monthly closes, AM briefs, promo measurement, growth coaching. ### Account Manager Briefing Packs Generate a consistent performance snapshot per AM: earnings mix, content output, creator-level KPIs. AMs walk into check-ins with answers — not "let me pull that and circle back." ### Period-End Closeouts Close monthly and quarterly cycles faster. Pre-structured summary and comparison views show exactly what moved and by how much. No ad-hoc spreadsheet assembly the night before payroll runs. ### Cross-Creator Benchmarking Line up creators side by side. Spot the outperformers and the underperformers. Redirect team hours toward the accounts with the highest upside — before another pay cycle slips past unnoticed. ### Promotion Impact Measurement Compare custom date windows around a campaign launch, pricing change, or content shift. Measure the lift in hard numbers — subscription dollars, PPV revenue, tip volume — not "felt like a good week." ### Operational Pulse Checks 90-second health check on any creator — or the full Fansly roster — during morning stand-up. Trend deltas tell you what needs attention today, before the issue becomes a quarterly write-down. ### Creator Growth Coaching Hand creators the same consolidated view your AMs use. They see which earnings categories grew, which stalled, and where to push next — backed by their own data instead of an AM hunch. ## Frequently asked questions ### What is AI Fan Summaries for Fansly? AI Fan Summaries is a consolidated Fansly reporting dashboard for agencies and solo creators. It pulls subscriptions, posts, messages, tips, and stream earnings into one filterable view across every creator on your roster — with built-in trend timelines and period-vs-period comparisons. ### Can I generate Fansly earnings reports across multiple creators? Yes. Pick a single creator, a pod of accounts, or your full roster from the multi-creator selector. Every chart, table, and KPI recalculates instantly to match the scope. Built for agency operations — one screen for a solo check-in, the same screen for a 60-creator quarterly review. ### How far back does the historical data go? AI Fan Summaries indexes 12 months of earnings history by default. Longer retention is available on paid plans. The historical performance timeline plots 3-, 6-, and 12-month windows side by side so you can spot inflection points without scrolling through CSV rows. ### Can I compare two different time periods side by side? Yes — period-vs-period comparison is core to the workflow. Pick any two date ranges (last month vs. previous month, this quarter vs. same quarter last year, pre-promo vs. post-promo) and the dashboard returns absolute deltas and percent shifts for every revenue line. ### Does this replace my spreadsheet workflow? For most agencies, yes. The dashboard consolidates the views you currently rebuild manually for AM briefs, month-end closes, and creator coaching. Export is still available if you need a CSV for finance — but the day-to-day reporting lives in the dashboard. ### Who is AI Fan Summaries built for — agencies or solo creators? Both. Solo creators use it to see exactly where their Fansly income compounds and where it stalls. Agencies use it for AM briefing packs, period-end closeouts, cross-creator benchmarking, and growth coaching. The same dashboard scales from one account to two hundred. ### Is AI Fan Summaries free to use? Yes, there is a free tier with 10 credits — enough to test the workflow on one creator account. Paid plans unlock multi-creator workspaces, longer historical retention, and higher refresh frequency. See the pricing page for current tiers. ### How does it connect to my Fansly account? You connect creator accounts through the dashboard one time. The connection uses authenticated API sessions — the same protocol the official Fansly app uses — not browser scraping or extensions. Data refreshes automatically. 5,000+ accounts connected with zero bans across 5+ years of operation. View on fansly-api.com: https://www.fansly-api.com/ai-fan-summaries --- # Fansly AI Financial Analytics: from gross revenue to true margin. Most Fansly agencies track top-line and call it finance. Almost none can tell you their real profit per creator after commissions, costs, and chargebacks. AI Financial Analytics closes that gap — so you always know exactly where the money goes. ## Features Track every transaction. Model future performance. Break down true profitability per creator, per month. All from a single dashboard wired to your live Fansly data. ### Real-Time Transaction Overview Every approval, refund, and chargeback across every creator on one screen. Filter by creator, date, or transaction type. Spot a refund spike at 11 a.m. instead of finding out at 11 p.m. — or worse, on next month's statement. ### AI Revenue Forecasting Four statistical models — Moving Average, Linear Regression, ARIMA, SARIMA — project revenue and churn up to 180 days out. Plan campaigns, set hiring budgets, and negotiate creator splits with numbers. ### Profitability Per Creator Net revenue, agency commission, every cost line, and your final margin — per creator, per month, in one table. Know exactly who prints money and who quietly costs you. Renegotiate the next contract — receipts in hand. ### Dynamic Cost Management Fixed, promo, chat, and referral costs plus commission milestones, all editable retroactively. Adjust a past month and historical margins recalculate instantly. No re-running reports, no exporting to Excel, no analyst. ### Historical Cost Snapshots Expand any creator row for the full financial timeline: net revenue, commission shifts, cost changes, milestone triggers, referral payouts — month over month. Audit-ready, no spreadsheet required. Defensible numbers when it matters. ### Daily Payout Automation Toggle daily payouts per creator from one modal. Set per-account payout behavior in seconds — a control Fansly does not give you natively. Important when your top earners want their money tonight, not next Tuesday. ## API endpoints Use grouped endpoint coverage to power core financial workflows: profitability tracking, forecasting, and transaction intelligence. ### Profitability Intelligence Calculate monthly creator profitability and pull historical records to track margin movement over time. ### Forecasting Models Project revenue or churn with statistical models so planning, campaign timing, and budget allocation stay data-backed. ### Transaction Intelligence Monitor payment outcomes and revenue composition using summary totals and by-type transaction grouping. ## Use cases Top agencies don't run on revenue alone. They run on margin, forecast accuracy, and chargeback discipline. Six financial workflows that separate $50K/month operators from $500K/month operators. ### Revenue Forecasting That Actually Works Choose Moving Average, Linear Regression, ARIMA, or SARIMA. Project revenue or churn up to 180 days out. Plan the Q4 hiring round on real numbers — not a hopeful slope drawn over yesterday's spreadsheet. ### Per-Creator Profitability Tracking Separate the creators who print money from the ones who quietly drain it. One table — net revenue, commissions, costs, your final take. Act on the margin gap before it costs you a quarter. ### Chargeback & Refund Monitoring Every payment outcome on one screen — approvals, refunds, disputes. Catch chargeback ratios crossing the processor danger zone (typically 1%) before someone in risk flags the account. Stop revenue leaks before they widen. ### Commission Milestone Automation Set threshold-based commission rules. Creator crosses $50K net? Their rate drops from 35% to 30% automatically. No manual adjustments, no missed thresholds, no "I thought you were going to update that" emails. ### Multi-Creator Roster Comparison Select one creator or the full roster. Every chart, table, and projection updates instantly. Compare profit margin across the roster and allocate your team's hours where the returns are highest — not where the personality dictates. ### Audit-Ready Financial History Every cost edit, commission shift, and milestone event is timestamped and immutable. Pull any creator's full financial record in seconds. Ready for tax season, contract renegotiations, due diligence, or the next investor deck. ## Frequently asked questions ### What is Fansly Financial Analytics? Fansly Financial Analytics is an AI-powered agency P&L dashboard built for Fansly agencies and large creator operations. It tracks revenue, models forecasts using ARIMA/SARIMA, breaks out per-creator profit after commissions and costs, and monitors chargebacks and refunds in real time — replacing the spreadsheets most agencies still run on. ### How accurate is the AI revenue forecasting? Four models run side by side — Moving Average, Linear Regression, ARIMA, and SARIMA — so you can compare projections against actuals on the same chart. Accuracy depends on data volume and seasonality, but for most agencies with 6+ months of history, the SARIMA model converges within ±5-10% over a 30-day window. ### How do per-creator profitability calculations work? Each creator row pulls net Fansly earnings, applies your configured agency commission, deducts fixed costs, promo spend, chat-team costs, and referral payouts, then surfaces the residual margin. Cost lines are editable and retroactive — adjust a past month and historical margins recalculate instantly. ### Can I track chargebacks and refunds in real time? Yes. The transaction overview surfaces every approval, refund, and chargeback as they happen — filterable by creator, date, or status. The dashboard flags accounts approaching the 1% chargeback ratio (the threshold most processors treat as a risk signal) so you can intervene before the account is restricted. ### Does this support commission milestone automation? Yes. Set threshold-based rules per creator — for example, drop commission from 35% to 30% when net Fansly revenue crosses $50,000. The system applies the new rate automatically going forward. No manual edits, no missed milestones, no awkward "we should have updated this two months ago" conversations. ### Can I edit past cost data? Yes. Costs are fully editable retroactively. Adjust a fixed-cost line for March, and March margins recalculate instantly across every dependent view — profitability, comparisons, historical timeline. Every edit is timestamped and stored for the audit trail. ### Is this audit-ready for tax filings? Yes. Every cost edit, commission shift, and milestone trigger is timestamped and immutable in the audit log. Pull any creator's full financial history in seconds. The export is structured for accounting software, tax preparation, or due-diligence packages. ### How is this different from native Fansly statements? Native Fansly statements show gross revenue per creator. They do not factor in your agency commission structure, fixed costs, promo spend, chat-team payroll, or referral fees — and they show one creator at a time. Financial Analytics rolls everything into a true agency P&L across your full roster. View on fansly-api.com: https://www.fansly-api.com/ai-financial-analytics --- # Fansly AI Chat Analytics: measure chatters like sales reps. Most agencies reply fast and hope. AI Chat Analytics shows which Fansly conversations drive revenue, which chatters close, and where every minute of response delay quietly cost you a PPV sale. ## Features From roster-wide Fansly chat KPIs down to individual message forensics. The metrics top agencies use to turn conversations into measurable, repeatable revenue. ### Messages Overview Dashboard Total messages, paid-message revenue, new-fan engagement rate, media sent, conversion rate, average response time, tip trends. Seven KPIs that tell you whether your chat operation is printing money or burning chatter hours. ### Response Times Per Creator How fast each chatter replies, and which chatter actually took the reply. Filter by creator, max response time, sender, or responder. One 30-minute delay = one lost $200 PPV. Now you know which chatter, which fan, which message. ### Multi-Creator Filtering & Search Pick creators, pick fans, pick date ranges. Every chart and table recalculates. Search across thousands of conversations and surface the exact message in seconds — no copy-paste between tools, no "let me get back to you." ### Message Detail Forensics Click any message: price, media count, tip status, pin state, queue origin, response time in seconds, who replied. Audit a conversation or settle a chatter dispute with receipts — not vibes. ### Chat Revenue Breakdown Revenue from paid messages, PPV, and tips — per creator and per chatter. The metric most agencies ignore — and the one that separates a $20K/month creator from a $200K/month creator with the same fan count. ### Chat Alerts & Notifications Alerts for unread piles, response-time SLA breaches, whale activity spikes. Chatters cannot watch every inbox 24/7. They do not have to — revenue-critical conversations stop falling through the cracks at 3 a.m. ## Use cases Revenue does not start at checkout — it starts in the conversation. Six workflows the highest-earning Fansly agencies use to turn chat from a cost center into a measurable revenue engine. ### Response Time as a Revenue Lever Faster replies close more sales — the data is unambiguous. Track average response time per chatter, set internal SLAs, and identify the closers who out-convert because they reply in minutes, not hours. Promote them. Coach the rest. ### PPV & Paid Message Performance Which paid messages convert? Which die in the queue? Track price points, open rates, and purchase rates per creator. Double down on the offers that earn — retire the ones that drain chatter hours and never sell. ### Mass Messaging Campaign Tracking Send counts, view rates, revenue per blast. Compare campaigns side by side. Stop guessing which mass-DM template works — measure it. Replicate the winner on the next 50 sends across the roster. ### Chatter Performance Scorecards Who replies fastest. Who closes the most message revenue. Who lets conversations die in the queue. Give chatters data-backed feedback — not vague complaints. Reward closers, coach the middle, replace the ones who cannot move. ### Conversation Monetization Audit Fans who chat daily but never buy. Conversations with high engagement and zero revenue. These are your warmest leads that nobody has asked the right way — yet. Find them. Brief the right chatter. Close the gap. ### Multi-Creator Chat Comparison Compare chat volume, response speed, conversion rate, and message revenue across the full Fansly roster. Find the chat strategies your top performers run. Replicate them across underperformers — same fans, same prices, better follow-through. ## Frequently asked questions ### What does Fansly Chat Analytics track? AI Chat Analytics tracks every metric that determines whether your Fansly chat operation makes money: message volume, paid-message revenue, PPV open and conversion rates, response time per chatter, tip totals, mass-messaging campaign performance, and per-creator chat revenue. Everything filterable by creator, fan, chatter, and date range. ### Can I measure individual Fansly chatter performance? Yes. Each message logs which chatter replied, response time in seconds, revenue generated, and the price point sold. Scorecards roll up to per-chatter dashboards: average response time, total message revenue, PPV conversion rate, tip volume. Hire, coach, and fire decisions with evidence instead of vibes. ### How does response time tracking work? Every reply is timestamped at the chatter and the fan side. The dashboard surfaces average response time per chatter, per creator, and per conversation. Set internal SLA thresholds (e.g. 5 minutes during business hours, 30 minutes overnight) and the system flags every breach — so you fix the delay before it costs another PPV. ### Does this work for Fansly mass messaging campaigns? Yes. Every mass DM blast is tracked individually — send count, view rate, click rate, revenue generated, revenue per recipient. Compare campaigns side by side to see which templates and price points convert. Roll the winning pattern out across the roster on the next send. ### Can I track PPV conversion rates per creator? Yes. The PPV performance view shows every paid message: price point, open rate, purchase rate, total revenue. Slice by creator to find which price tiers each account converts on. Most agencies discover that their best creator and their worst creator are charging the same price for very different content — and the data fixes it. ### Does this cover multi-account agency rosters? Yes — multi-creator support is built in. Connect every Fansly account on your roster, then filter across all creators or drill into one account. Compare chat volume, response speed, conversion, and message revenue side by side. Find the chat strategy your top performer uses and replicate it across the rest. ### Is the chat data real-time? Messages and revenue update in near-real-time — typically within seconds of the event happening on Fansly. Alerts for unread piles, SLA breaches, or whale activity fire in real time. The 90-minute reporting lag most agencies live with on spreadsheets does not exist here. ### Is AI Chat Analytics free to use? Yes, there is a free tier with 10 credits to test on one creator. Paid plans unlock multi-creator workspaces, full chatter scorecards, longer historical retention, and higher API quota. See the pricing page for current tiers. View on fansly-api.com: https://www.fansly-api.com/ai-chat-analytics --- # The Fansly CRM: know every fan, keep every whale. Everything your agency knows about its fans lives in stale spreadsheets and chatters’ heads. The Fansly CRM replaces both — fan tracking, subscriber segmentation, and retention tools in one workspace. ## Your current CRM is whatever the chatters remember. A fan messages at 3 AM. Whale or lurker? Nobody remembers. With live profiles — spend, history, churn risk — any chatter knows in 30 seconds. - $6,000/year — one churned whale nobody noticed - One chatter quits = fan relationships walk out with him - One-price PPV blasts — whales underpriced, freeloaders spammed ## How agencies fake it today — and what changes - **Who is this fan?** — Today: Scroll history, guess, ask in Telegram. With the Fansly CRM: Live profile, spend, history, AI summary — 30 seconds. - **Whale tracking** — Today: A spreadsheet, updated whenever someone remembers. With the Fansly CRM: Live top-spender list, always know who to prioritize. - **Churn detection** — Today: Noticed two weeks late, if at all. With the Fansly CRM: Alerts when a whale goes quiet, before the renewal date. - **Shift handoff** — Today: Voice notes and vibes. With the Fansly CRM: Notes attached to the fan, not the chatter. - **Mass messaging** — Today: One price, whole roster, pray. With the Fansly CRM: Segments by spend tier, right offer, right fan. - **New chatter onboarding** — Today: Weeks of “who’s this guy?”. With the Fansly CRM: Full context day one, on every fan. ## Features Everything your team fakes with spreadsheets and memory, pulled live from the Fansly API into one workspace. ### Know any fan in 30 seconds, on any shift A new chatter continues the conversation mid-sentence — spend, history, PPV, tips, one record. ### Send the right offer to the right fan “Whales active this week.” “Expired subs who tipped.” Segments in clicks, messages in minutes. ### Catch a whale leaving before he’s gone 10% of fans drive 80% of revenue. Get alerted the moment a top spender goes quiet — while a win-back still works. ### Greet every new sub while interest is hottest Welcome messages the minute a fan subscribes, win-backs for quiet fans, scheduled sends — on autopilot. ### Hand off shifts without losing the thread A one-paragraph AI briefing per fan: who he is, what he buys, what he responds to. Shift changes stop losing context. ### Grow your roster: run 20 creators like you run one Sign more creators without quality dropping — account-wide retention plays and per-creator comparison show where effort pays best. ## Use cases Nobody can hold 2,000 fans in their head. What the CRM does for each role on your team. ### See the roster like a P&L Which fan base spends most per head, where retention pays off, which fans follow three of your creators. Scale from 5 to 20 creators without hiring 20 more chatters. ### Retention as a pipeline, not a panic Top 50 spenders flagged, watched, assigned. A whale goes quiet for three days — someone reaches out before the renewal date. Lapsed spenders get win-backs automatically. ### Know every fan instantly Spend history, AI summary, team notes, what was promised and when. The $50 bundle goes to proven buyers, the $10 teaser to fence-sitters. Better closes, bigger commissions. ## Your roster, your rules The CRM holds your agency’s memory — you hold the keys. Access, automation, and data stay under your control. ### Per-account access You decide which creators connect; revoke any connection instantly. ### Read-first by design Nothing reaches a fan you didn’t approve; automation runs your rules. ### Your data, exportable Full export any time. If you leave, the memory leaves with you. ### Team permissions Chatters see only assigned accounts; leavers lose access instantly. ## Frequently asked questions ### Is this safe for my creators’ accounts? The CRM reads data through the Fansly API. You control which accounts are connected, every connection is revocable instantly, and nothing about the CRM impersonates the creator — it organizes what your team already sees, it doesn’t act as the creator. ### Is creator and fan data safe? Fan and revenue data is scoped per connected account, chatters only see the accounts they’re assigned to, and you can export or delete everything at any time. Your roster’s data is yours. ### What is a Fansly CRM? A CRM (customer relationship management) for Fansly treats every subscriber like a customer record: total spend, subscription history, purchases, conversation context, and churn risk in one profile. Instead of an inbox of anonymous usernames, your team works from fan profiles — and messages convert because they’re informed, not generic. ### Does Fansly have a built-in CRM? No. Fansly gives creators an inbox and a basic subscriber list — no spend history per fan, no segmentation, no churn alerts, no team features. That’s the gap this CRM fills, pulling live data from every connected account. ### Can I segment my Fansly subscribers? Yes — by spend tier, activity, subscription status, churn risk, or any combination. Every segment is actionable: message it, export it, or hand it to a chatter. ### Does it automate Fansly messaging? Yes. Welcome messages for new subscribers, scheduled sends, and re-engagement sequences for quiet fans. Automated and manual messages share one conversation history, so chatters always see the full picture. ### Does it work for agencies with multiple creators? Yes — multi-creator support is core. Connect every account on your roster and get one CRM across all of them: cross-creator fan overlap, roster-wide segments, per-creator comparisons. Chatters see only the accounts they’re assigned to. ### Will this replace our chatters? No. It replaces the database they’ve been forced to keep in their heads. Chatters still build the relationships and close the sales — they just stop starting every conversation blind. ### What does it cost? Free to start — test the CRM on one creator, no credit card. Paid plans unlock multi-creator workspaces, segmentation, automation, and longer retention, scaling with your roster. See the pricing page for current tiers. View on fansly-api.com: https://www.fansly-api.com/fansly-crm --- # The Fansly video downloader: your whole catalog, saved in original quality. Three years of content, hundreds of videos — and the only copy lives on Fansly. The Fansly video downloader backs up your full catalog in original quality: batch download, PPV included, no browser extension. ## Your only copy lives on someone else’s platform. Years of videos, one host. A locked account, a deleted post, a policy change — and the catalog your business runs on is gone. Sketchy extensions aren’t a backup plan. - Hundreds of videos — zero local copies - Extension rippers: compressed quality, broken logins, risked accounts - PPV and message videos — invisible to every scraper tool ## Rippers, recorders, and the real thing - **Video quality** — Extensions & recorders: Re-compressed rips, watermarked frames. With the Fansly Video Downloader: Original files, exactly as Fansly stores them. - **Whole catalog** — Extensions & recorders: One video at a time, babysitting tabs. With the Fansly Video Downloader: Batch download, the full library in one run. - **PPV & message videos** — Extensions & recorders: Invisible — they only see public posts. With the Fansly Video Downloader: Included, every video you sent or sold. - **Account safety** — Extensions & recorders: Browser hacks and shared logins. With the Fansly Video Downloader: API access, on accounts you connect. - **Organization** — Extensions & recorders: Random filenames in a Downloads folder. With the Fansly Video Downloader: Named, foldered ZIP archives, ready to restore. - **Repeat backups** — Extensions & recorders: Manual, whenever you remember. With the Fansly Video Downloader: Automated via API, backups that run themselves. ## Features Every video on the account, pulled through the Fansly API into archives you actually own. ### Back up your whole catalog in one run Every video on the account — posts, stories, vault — queued in one run and delivered as organized ZIP archives. No tab babysitting. ### Get the original source file, not a compressed rip Downloads pull the source files Fansly stores — full resolution, no re-compression, no screen-capture watermarks. ### Save the videos rippers can’t even see Paid unlocks and DM attachments export alongside your posts — the videos extension tools can’t reach. ### One clip or three years — your pick Filter by date range, content type, or a single clip. Pull one video or the entire catalog. ### Backups that run themselves, on your schedule Trigger exports via the REST API or no-code tools — new videos back up without anyone remembering to run it. ### More than videos when you need it Messages, fans, transactions, payouts — the full Fansly Downloader exports every data type, not just media. ## Use cases A catalog is an asset. What the video downloader does for each role that depends on it. ### Your catalog, safe off-platform Three years of content is the business’s net worth. One automated backup keeps a local copy of every video — whatever happens to the account, the catalog survives. ### Archive every creator on the roster Creators join, creators leave. Export full video libraries at onboarding and offboarding, keep organized archives per creator, and never lose deliverables with a departing model. ### Video pipelines without the scraping Pull videos programmatically via the REST API — migrations, re-upload tools, AI training sets — without maintaining a headless browser that breaks every Fansly update. ## The safe way to download Your videos move through the Fansly API on accounts you authorize — no extensions, no shared logins, no gray-zone tooling. ### Only accounts you connect Works on accounts you own or manage — connect, authorize, download. ### No browser hacks API access instead of extensions; nothing injected into Fansly. ### Your archives, your storage Download, verify, store wherever you want — exports are yours. ### Per-account team access Team members touch only the accounts they’re assigned. ## Frequently asked questions ### Is this safe for my Fansly account? Downloads run through the Fansly API on accounts you connect — no browser extensions, no screen automation, nothing injected into Fansly’s site. You control which accounts are connected, and every connection is revocable instantly. ### Can I download videos from any Fansly account? No. The downloader works only on accounts you own or manage and have connected. It’s a backup tool for your own catalog — not a tool for ripping other creators’ content. Connect an account you’re authorized on, and every video on it becomes exportable. ### What is a Fansly video downloader? A Fansly video downloader exports the videos from a Fansly account to storage you control. This one connects through the Fansly API and pulls the original source files — posts, stories, vault, PPV, and message attachments — in batch, so a full catalog backs up in one run instead of video by video. ### Does Fansly have a built-in video download option? No. Fansly lets you view your content but offers no bulk export — no way to batch-download a catalog, pick what to pull, or save message videos from the native interface. That’s the gap this downloader fills, through the API rather than screen scraping. ### What quality are the downloaded videos? Original quality. The downloader pulls the source files Fansly stores rather than re-recording or re-compressing, so what you archive is exactly what was uploaded — full resolution, no watermarks, no generation loss. ### Can I download PPV and message videos? Yes. Videos sent in DMs, sold as PPV, or attached to messages export alongside posted content — from connected accounts. These are the files extension-based tools can’t see at all, because they only touch public pages. ### Can I automate recurring backups? Yes. Trigger exports through the REST API or no-code tools like n8n, Zapier, and Make.com, so new videos back up on a schedule. Combined with organized ZIP archives, the catalog stays current without anyone remembering to run it. ### Can I export more than videos? Yes — the full Fansly Downloader exports every data type: photos, messages, fans, transactions, payouts, and tracking links. This page covers the video side; for complete account exports, see the Fansly Downloader page. ### What does it cost? Free to start — 10 credits to test on one creator, no credit card. Paid plans scale with connected accounts and unlock higher API quota and larger exports. See the pricing page for current tiers. View on fansly-api.com: https://www.fansly-api.com/fansly-video-downloader --- # The Fansly unlocker: your whole vault, one API away. Your top-earning content is locked in vault folders, buried chats, and archived posts. The Fansly unlocker opens your own catalog via API — media access, content management, and vault workflows for accounts you connect. ## Your best content is locked away from your own team. The PPV that printed money in March? Somewhere in a vault folder. The welcome clip? On a chatter’s phone. Your catalog earns once and disappears. - Top sellers buried in unsearchable vault folders - Chatters re-request media the account already has - Content earns once, then never sells again ## Junk-drawer vault vs. working catalog - **Finding a file** — In the Fansly app: Scroll vault folders and guess. With the Fansly unlocker: Listed and structured, every vault item via API. - **Reusing best sellers** — In the Fansly app: Re-upload from someone’s phone. With the Fansly unlocker: Pull and reattach, the exact file that sold. - **Message media** — In the Fansly app: Lost in thousands of chats. With the Fansly unlocker: Chat galleries listed, every sent file findable. - **Content audits** — In the Fansly app: Nobody knows what exists. With the Fansly unlocker: Full media inventory, across every connected account. - **New chatter setup** — In the Fansly app: “Ask Maria where the clips are”. With the Fansly unlocker: Same catalog for everyone, from day one. - **Building tools** — In the Fansly app: Manual downloads and uploads. With the Fansly unlocker: Media endpoints, list, fetch, attach programmatically. ## Features Vault, chats, and archived posts — the catalog you already paid for, opened through the Fansly API. ### Open your whole vault programmatically List vault folders and media across connected accounts — every file you own, structured and searchable via API. ### Resurface the PPV that already sold Chat media galleries list every file sent and sold, so best sellers get reused instead of remade. ### Give every chatter the same catalog No more asking who has the clip — the full media library is one API call away on every shift. ### Audit content across the whole roster Full media inventory per account: what exists, where it lives, what’s been sent — before you plan the next shoot. ### Automate content workflows end to end Attach vault media to messages and posts via API — scheduled reposts, PPV re-sends, no-code flows included. ### Back up everything that you unlock Pair with the Fansly Downloader to export the media you unlock — original quality, organized archives. ## Use cases A catalog nobody can reach earns nothing. What the unlocker does for each role on your team. ### Run content ops, not scavenger hunts Know what content exists, what performs, and what’s ready to re-send. Plan shoots around gaps instead of guesses — and stop paying for content you already own. ### The right clip, attached in seconds A whale asks for more at 2 AM — the catalog answers. Search the vault, grab the file that fits, close the sale while he’s still online. ### Content tooling on real endpoints Vault, media, and post endpoints documented and stable — build content managers, repost schedulers, and media pipelines without touchy browser automation. ## Unlocks your content. Nobody else’s. The unlocker works through the Fansly API on accounts you connect — your vault, your media, your paywall intact. ### Only accounts you connect Opens content on accounts you own or manage — nothing else. ### Not a paywall bypass Other creators’ locked content stays locked. Full stop. ### Permission-scoped access Team members reach only the accounts they’re assigned. ### Revocable any time Disconnect an account and access ends instantly. ## Frequently asked questions ### Is this safe for my Fansly account? The unlocker works through the Fansly API on accounts you connect — no browser automation, no shared logins, nothing injected into Fansly’s site. You control which accounts are connected, team access is permission-scoped, and every connection is revocable instantly. ### Can I unlock other creators’ paywalled content? No. The Fansly unlocker is not a paywall bypass and cannot access anyone else’s locked content. It works exclusively on accounts you own or manage and have connected — opening programmatic access to your own vault, media, and posts. ### What is a Fansly unlocker? A Fansly unlocker opens programmatic access to the content locked inside your own Fansly account — vault media, chat attachments, and archived posts. Instead of scrolling app folders, you list, retrieve, and reuse your catalog via API: search it, attach it to messages, feed it into workflows. ### Does Fansly have built-in vault management? Fansly’s vault is folders in the app — no search across accounts, no media inventory, no way to plug content into workflows or tools. The unlocker adds that layer through the API: structured listings, chat galleries, and programmatic attach for messages and posts. ### What content can I access? Everything on connected accounts: vault media and vault lists, chat and message attachments, and wall posts — across every account on your roster. The same 200+ endpoint surface that covers accounts, fans, messages, media, posts, and vaults. ### Can I reuse content in messages and posts? Yes. Attach vault media to chats, mass messages, and wall posts via the API — re-send proven PPVs, schedule reposts, or wire it into no-code tools like n8n, Zapier, and Make.com. The file that sold in March can sell again tonight. ### Can I export what I unlock? Yes. Pair the unlocker with the Fansly Downloader to export media in original quality as organized archives — back up the catalog you open, or move it wherever your workflow lives. ### What does it cost? Free to start — 10 credits to test on one creator, no credit card. Paid plans scale with connected accounts and unlock higher API quota. See the pricing page for current tiers. View on fansly-api.com: https://www.fansly-api.com/fansly-unlocker --- # Guides --- # Win Back Lost Fans: A Solo Creator's Playbook for Churn Prevention Canonical: https://www.fansly-api.com/blog/fansly-churn-prevention-creators > Learn how solo creators can leverage automation and API software to reduce subscription churn and recover lost fans effectively. Keywords: automation tools, api software, api process, api automation Monthly subscriber churn represents the single largest income leak in the creator economy today. While independent creators frequently spend over 60% of their operational energy feeding top-of-funnel acquisition channels, subscription attrition systematically dismantles compound earnings. In 2026, re-engaging a lapsed subscriber costs five to seven times less than acquiring a net-new member, and winback campaigns convert at 8% to 15%—climbing up to 30% when triggered within the first month of cancellation. For solo creators lacking the dedicated staffing of massive management agencies, manual winback tracking is operationally impossible. Solving this bottleneck requires programmatic retention: deploying modern automation tools and robust API software to detect expirations in real time, segment subscribers by historical value, and deliver personalized renewal incentives on autopilot. ## What is Creator Subscription Churn? Before deploying a winback strategy, creators must understand that churn bifurcates into two distinct behavioral mechanisms. Treating all cancellations the same is a critical error in subscription management. ### Voluntary Churn Voluntary churn accounts for 60% to 75% of subscription losses. This occurs when a subscriber makes a conscious decision to disable auto-renew. The root causes are typically behavioral, such as content saturation, unread direct messages, perceived lack of posting frequency, or financial re-budgeting. Remediation requires tiered access incentives, targeted renewal discounts, and personalized re-engagement. ### Involuntary Churn Involuntary (or passive) churn accounts for 20% to 40% of subscriber losses. This occurs when a fan intended to remain active, but the billing transaction failed. As analyzed by [Churnkey (2026)](https://churnkey.co/guides/reduce-involuntary-churn) across 5.4 million failed payments, declines stem primarily from soft declines (temporary bank fraud alerts, processor timeouts) and hard declines (expired cards). Studies show that automated recovery flows can recover 40% to 70% of these failed renewals without any changes to pricing or content, according to [RecurX (2026)](https://recurx.app/subscription-churn-benchmarks). ## 2026 Creator Retention Benchmarks In recurring membership models, net subscriber count is a lagging vanity metric. A creator page that gains 200 subscribers but loses 180 every month remains structurally fragile. Current 2026 industry data reveals the true economic weight of churn: - **Month-One Drop-off:** According to [xcelerator Model Management (2026)](https://onlyfanscourse.com/blog/retention-growth-metrics-dashboard/), roughly 50% of new subscribers cancel after month one. Baseline monthly churn across subscription fan pages hovers between 30% and 50%. - **Top-Tier Baselines:** High-performing direct-response creator operations with mature retention infrastructure keep monthly churn bounded between 15% and 25% ([Everything-PR, 2026](https://everything-pr.com/how-onlyfans-creators-actually-make-money-in-2026)). - **The LTV Multiplier:** As highlighted in [Zanfia's Digital Creator Study (2026)](https://zanfia.com/blog/how-to-reduce-subscription-churn-for-digital-creators-2026-tactics/), reducing monthly churn from 10% to 5% doubles total subscriber lifetime value without generating an extra click of cold traffic. - **Return Rate:** Data from [Recurly's 2026 State of Subscriptions report](https://recurly.com/content/state-of-subscriptions-report/) reveals that former subscribers drive nearly 1 in 4 (25%) new sign-ups. Churned subscribers already understand your brand and have overcome the hurdle of entering payment credentials. ## The 3-Phase Automated Winback Cadence Because solo operators cannot spend hours scanning log files, an automated 3-phase re-engagement sequence strikes the optimal balance between high conversion and non-intrusive messaging. ### Phase 1: Day 1 Post-Expiration (The Soft Check-in) - **Goal:** Acknowledge the lapse gracefully without aggressive commercial discounting. - **Mechanism:** Trigger an automated direct message within 24 hours of the subscription expiring. - **Strategy:** Address potential involuntary churn first. Message angle: *"Hey \[Name\], noticed your sub lapsed! Just wanted to make sure you didn’t lose access by accident with a card error. If you’re taking a break, thank you so much for hanging out. I left a short preview clip in your DM so you can see what’s dropping this week!"* ### Phase 2: Day 7 Post-Expiration (The Targeted Incentive) - **Goal:** Reactivate fans before emotional detachment sets in. - **Mechanism:** Research from the [Subscription Index (2026)](https://www.subscriptionindex.com/guides/win-back-campaigns) confirms that generic 50% discounts devalue premium brand perception. Instead, offer a 15% to 25% renewal incentive or a bonus vault media unlock. - **Strategy:** Provide a limited-time coupon link valid for 48 hours, highlighting exclusive upcoming content drops to create urgency. ### Phase 3: Day 30 Post-Expiration (The Re-Activation) - **Goal:** A final touchpoint prior to archiving the contact into a passive broadcast cohort. - **Mechanism:** Provide an aggregated digest of the highest-rated posts over the last month, bundled with a multi-month renewal discount (e.g., 20% off a 3-month bundle). ## Architectural Blueprint: Automating Churn with Fansly API Building an automated winback engine does not require an enterprise engineering squad. Modern event-driven API automation allows independent operators to configure enterprise-grade retention systems using no-code integration orchestrators like n8n, Make.com, or Zapier. The [Fansly API](/) provides a production-grade developer platform that exposes over 200 live endpoints and real-time HMAC webhooks specifically designed for creator CRMs and mass-messaging tools. ### Step-by-Step API Process for Winback Campaigns 1. **Event Ingestion (Real-Time Webhooks):** Rather than running scheduled cron jobs that poll a database and burn API credits, developers utilize the `subscription.expired` webhook documented in the [Fansly API Integration Guide](/blog/fansly-api-integration-guide). When a fan's auto-renew fails, the API instantly dispatches a webhook payload to the creator's receiver. 2. **Spend Segmentation:** The API process then queries subscriber data. It lists the current roster with `GET /api/fansly/{account}/subscribers` ([Fansly API Documentation](https://docs.onlyfansapi.com/api-reference/fansly/subscribers/list-subscribers)), compares it with the previous day's snapshot to spot who lapsed, and evaluates each lapsed fan's historical spend. High-value supporters (e.g., $200+ LTV) can be routed to a VIP channel for personal 1-on-1 outreach, while standard tiers enter the automated drip. 3. **Automated Messaging Execution:** For standard tier subscribers, the workflow registers the fan in a 3-stage drip sequence hosted within a no-code engine. It executes Phase 1, 2, and 3 messages via the `POST /{account_id}/mass-messaging` endpoint ([API Docs](https://docs.onlyfansapi.com/api-reference/fansly/mass-messaging/send-mass-message)), seamlessly attaching teaser vault media based on the fan's timezone. 4. **The Churn Cancellation Loop:** If the fan renews at any point during the 30-day sequence, the `subscription.renewed` webhook triggers immediately. This instantly halts pending winback drips and returns the fan to active subscriber status, preventing embarrassing or redundant discount messages. ## Best Practices for Solo Creators To maximize the effectiveness of your retention workflows, keep these critical strategies in mind: - **Protect Pricing Integrity:** Never issue desperation discounts (60%–75% off) within hours of cancellation. This trains active subscribers to intentionally cancel just to fish for cheaper rates. Cap your winback discounts at 15%–25% or offer bonus value instead of slashing base prices. - **Prioritize the First 7 Days:** Winback is highly time-sensitive. Re-engaging subscribers within the first 7 days of expiration recovers up to 30% of lost revenue. Waiting 60+ days drops reactivation rates below 5%. - **Automate the Dunning Bridge:** Separate payment decline churn from active cancellations. By instantly triggering a grace-period alert for involuntary failures, you ensure fans update their card details before their access is fully revoked. Mastering retention is no longer optional for creators aiming for predictable recurring revenue. By adopting reliable automation tools and integrating sophisticated backend workflows, solo creators can replicate the complex retention infrastructure previously reserved for seven-figure creator agencies—operating efficiently, recovering lost revenue, and scaling sustainably month after month. --- # Fansly Tip Alerts & Instant Gratification: Setting Up Private Alerts for Discord or Telegram Canonical: https://www.fansly-api.com/blog/fansly-tip-alerts-discord-telegram > A guide on using no-code automation to receive real-time Fansly notifications in Discord or Telegram to increase fan engagement and reduce creator burnout. Keywords: build app no code, n8n automation, real time api, no code tools For independent adult and subscription creators on Fansly, immediate response time is one of the most powerful levers for maximizing fan lifetime value (LTV) and tip volume. However, relying on browser tabs forces creators into an "always-on" state of vigilance that inevitably leads to cognitive overload and burnout. Fortunately, you no longer need complex engineering skills to solve this problem. Today, creators and boutique agencies can build an app with no code to route instant, private alerts directly to mobile devices. By leveraging intuitive no-code tools, you can set up free, customized notifications via Telegram or Discord whenever you receive a tip, custom request, or DM unlock, allowing you to respond rapidly without staying glued to a dashboard. ## Why Is Instant Gratification Crucial for Monetization? Digital consumers and subscription fans operate under heightened expectations of immediacy. Research compiled by [SumGeniusAI](https://sumgenius.ai/blog/instagram-dm-response-time-cost-calculator-2025/) highlights a steep decay curve in engagement based on lead response times. Responding within 1 minute increases lead conversion rates by 391%. Furthermore, inbound inquiries answered within 5 minutes are 21 times more likely to convert compared to those answered after 30 minutes. In the pay-per-view (PPV) messaging space, high-intent spenders frequently make custom requests during impulsive, emotionally charged sessions. When a fan tips $50 or unlocks a high-tier video, their dopaminergic engagement is at its peak. A prompt response within minutes turns a single transactional tip into an extended tipping session. Waiting just one to two hours causes conversion rates to drop to 3–5%, and they plummet below 2% after 24 hours. ## What Causes the "Always-On" Creator Burnout? While speed drives revenue, manual monitoring is physically and emotionally unsustainable. According to data published by [Sozee](https://sozee.ai/resources/prevent-creator-burnout-adult-content/), 62% of digital creators report experiencing burnout. This is often exacerbated by the fact that 69% of creators struggle with financial instability, creating an anxiety loop where stepping away from the screen feels like forfeiting critical income. Content analyst Drew Mirandus notes in [*Creator Burnout Isn’t About Algorithms*](https://drewmirandus.com/2026/06/17/creator-burnout-staying-visible-after-posting/) that modern fatigue stems from constant accessibility. Burnout starts "during the stretch of time where you are technically 'done' yet still exposed." As highlighted by [GetFanSee in their 2026 industry analysis](https://getfansee.com/blog/how-to-avoid-burnout-as-an-adult-content-creator-in-2026/), the fear of missing DM replies traps solo creators in 14-hour screen-time cycles. Native notifications fail to solve this because browser alerts require active tabs, and native emails mix transactional receipts with zero-dollar likes. Even third-party community bots like [NotiFansly](https://notifansly.xyz/) are designed to send public livestream alerts to fans, rather than private, back-office operational alerts to the creator. ## How Do Real-Time Alerts Work? To receive instant notifications without maintaining an open tab, an external system must detect when an event occurs using a robust real-time API. Legacy architectures rely on polling—where a script queries the platform every 60 seconds to check for new tips. This method is computationally inefficient, introduces a 45–90 second latency delay, and risks IP blocking due to rate limits. Conversely, real-time HMAC webhooks push an HTTP payload the exact microsecond an event fires. As detailed in the [Fansly Webhooks Guide](/blog/fansly-webhooks-guide), webhooks completely eliminate "polling math" and offer an event-driven model with sub-second execution, securely protected by cryptographic signatures. ## Step-by-Step Guide: Setting Up Private Alerts for Telegram or Discord Building a custom notification pipeline is straightforward. Here is the step-by-step framework to establish private alerts without writing complex code. ### Step 1: Establish Your Destination Endpoint First, decide where you want to receive your alerts on your mobile device. - **For Telegram:** Message `@BotFather` on Telegram to generate a new bot and copy the Bot API Token. Start a chat with your new bot and extract your personal `chat_id` via a tool like `@userinfobot`. Telegram is outstanding for solo creators who want custom phone vibrations specifically for VIP alerts. - **For Discord:** Create a private Discord server or a hidden channel accessible only by you (or your assistant). Navigate to Channel Settings > Integrations > Webhooks > New Webhook, and copy the Webhook URL. ### Step 2: Configure n8n Automation Logic Next, act as the routing engine using a visual workflow builder. Setting up n8n automation allows you to filter out the noise and only trigger mobile alerts for actionable, high-value events. 1. **Create a Webhook Trigger Node:** In your n8n workspace, create a workflow with a Webhook node set to POST. This generates a dedicated production webhook URL. 2. **Add a Filter Condition:** Add an IF node to evaluate dollar thresholds. For example, configure it to only pass the alert through if `event_type == 'tip.received'` AND the amount is greater than or equal to $15. 3. **Set the Action Node:** For Telegram, add the Telegram Node, paste your bot credentials, and construct a dynamic message (e.g., `🚨 New Tip: $50 from @username!`). For Discord, use the Discord Node to send a rich JSON embed card with a direct URL back to the specific conversation. ### Step 3: Register the Webhook with Fansly API Finally, connect your automation workflow to the platform infrastructure. In your [Fansly API](/) dashboard, register the production URL generated by n8n. Select your target subscription events (such as `tip.received`, `sale.completed`, or `message.received`) and configure the signing secret. This ensures your workflow can cryptographically validate incoming payloads using HMAC-SHA256, protecting your private pipeline against spoofing attacks. ## How Does Fansly API Empower Creator Operations? While individual creators can configure basic private notification channels, agencies and developer teams can scale this architecture across hundreds of creator accounts simultaneously. [Fansly API](/) serves as a foundational bridge in the creator management landscape, providing a production-grade developer platform. By exposing over 200 live endpoints alongside real-time HMAC webhooks, Fansly API enables not just basic event alerts, but complex programmatic response actions—such as automatic thank-you messaging, custom media delivery, and CRM synchronization. This infrastructure allows agencies and non-technical creators alike to establish enterprise-grade operations at negligible infrastructure costs, completely bypassing traditional polling limits and platform throttling. ## Conclusion In subscription creator monetization, response time is a direct multiplier of average order value. Implementing private, real-time webhooks via Telegram or Discord allows you to capture peak tipping momentum within seconds while freeing yourself from the cognitive prison of the browser tab. By pairing reliable API infrastructure with modern visual workflows, you can easily build an app with no code that transforms unstructured notification noise into prioritized, actionable alerts. Protect your work-life boundaries while ensuring your VIP fans receive the immediate attention that drives long-term revenue. --- # Automating Fansly Media Uploads & FYP Previews: Streamlined Workflows for Solo Creators Canonical: https://www.fansly-api.com/blog/fansly-media-upload-automation > How solo creators use the Fansly API to automate media uploads and FYP previews, cutting manual upload work and boosting algorithmic discovery. Keywords: develop apps, automation tools, build tools, api posts The creator economy has reached an inflection point in 2026 where operational overhead, rather than content creation, represents the largest barrier to sustainable growth. For solo creators operating on subscription platforms, the administrative tax of uploading high-resolution video, configuring granular paywalls, and organizing vault albums consumes hours of productive capacity. By shifting from manual browser drag-and-drop interfaces to programmatic pipelines powered by the Fansly API, creators and agencies can deploy powerful automation tools that seamlessly handle media ingestion and algorithmic discovery. ## What is Automated Media Ingestion for Creators? Automated media ingestion is the programmatic process of uploading, categorizing, and publishing content to a platform without manual human intervention. Instead of requiring a creator to sit at a browser—manually dragging files, waiting for UI transcodes, selecting paywall tiers, and configuring algorithm tags—an automated pipeline handles these tasks in the background. For solo operators, this means a video exported to a local computer folder can be automatically compressed, uploaded to a content delivery network (CDN), tagged into a specific vault album, and scheduled for algorithmic discovery while the creator sleeps. ## Why Solo Creators Need Workflow Automation in 2026 While independent creators value creative freedom, they frequently shoulder the combined responsibilities of a media editor, platform manager, and community strategist. The result is a severe imbalance between content production and administrative management. According to recent analysis by [AEstruct on LinkedIn](https://www.linkedin.com/posts/emilfreund_the-other-side-of-the-creator-economy-activity-7431732975123214336-bs4M), only 46% of a creator's working time is spent producing content, while 52% is spent on administrative distribution, file management, and platform logistics. Additional industry benchmarks paint a clear picture of the operational burden: - **Massive Time Deficits:** Research published by [Snippet](https://usesnippet.app/blog/creator-burnout-statistics-real-cause) reveals creators spend between 15 to 20 hours per week on unpaid administrative and operational labor. - **Epidemic Burnout Rates:** A comprehensive 2026 survey by [The Creator Economy](https://thecreatoreconomy.com/post/creator-burnout-78-percent-mental-health-2026) found that 78% of creators report burnout affecting their physical health and motivation. This burnout is most acute among mid-tier solo creators (50,000 to 500,000 followers) who generate substantial revenue but lack the agency management teams required to absorb backend operations. Over half of a creator's workweek is consumed by administrative friction. To combat this, technical operators must build tools that decouple platform logistics from creative output. ## How Does the Fansly Algorithm Work (FYP Requirements)? Unlike closed-ecosystem platforms that lack native discovery and force creators to market heavily on external social networks, Fansly features a built-in algorithmic discovery engine: the For You Page (FYP). However, reaching new audiences through the FYP requires precise technical inputs. According to official guidelines from the [Fansly Help Center](https://help.fansly.com/en/articles/12836984-for-you-page-fyp), the FYP system relies on strict content-level signals to evaluate and distribute media: 1. **Mandatory Free Previews:** The FYP algorithm will reject or fail to surface paywalled (Pay-Per-View) or subscription-locked posts that lack an unlocked preview. Creators must attach a free teaser clip or image alongside the locked asset. 2. **Explicit Targeting via `fypFlags`:** Content must explicitly opt into the recommendation engine. In the underlying data model, this requires passing a bitwise integer, such as `fypFlags: 4`, which signals internal scrapers to index the post into discovery clusters. 3. **Timeline vs. FYP Decoupling:** Creators can route posts exclusively to the FYP without cluttering their main timeline, preserving a curated aesthetic for existing subscribers. ## Step-by-Step Guide: Automating Fansly Uploads and API Posts To eliminate the manual drag-and-drop bottleneck, you can automate media processing through a structured, asynchronous ingestion architecture using authenticated endpoints. ### Step 1: Implementing Two-Stage Asynchronous File Uploads Because 4K video files are bandwidth-heavy, the [Fansly API Media Upload Architecture](https://docs.onlyfansapi.com/api-reference/fansly/media/upload-media) enforces a non-blocking, two-step upload process to ensure stability. First, initiate the binary upload via a `multipart/form-data` request: ```http POST /api/fansly/{accountId}/media/upload Headers: { "x-api-key": "YOUR_API_KEY" } Body: file=@video_master.mp4 ``` The server responds with an HTTP status `201 Created` and a background `jobId`. Next, poll the job status endpoint (e.g., every 3 seconds) at `GET /api/fansly/{accountId}/media/upload/{jobId}/status`. Once the state transitions to `completed`, the API returns the immutable `mediaId` hosted across the platform's CDN. ### Step 2: Automating Vault Album Organization Instead of manually dragging uploaded media into nested UI folders, programmatic tools can organize content instantly. By accessing the [Fansly API Reference](https://docs.onlyfansapi.com/api-reference/fansly), scripts can retrieve existing album IDs via `GET /api/fansly/vault/albums` and sort incoming assets into tagged buckets (e.g., "Teasers", "PPV Bundles") the moment the file upload completes. ### Step 3: Composing API Posts with Previews and Paywalls When publishing locked content intended for algorithmic reach, you must structure automated API posts to tie the locked full-length `mediaId` to an unlocked `previewId`, while also setting monetization rules. According to the [Fansly API Post Composition Documentation](https://docs.onlyfansapi.com/api-reference/fansly/posts/send-post), the JSON payload should look like this: ```json { "content": "Exclusive weekend preview clip! Unlock the complete 15-minute set below 👇 #fyp", "mediaIds": [ { "mediaId": "831751193247105025", "previewId": "527804380229935104" } ], "access_type": ["ppv"], "price": 9.99, "fypFlags": 4, "replyPermissionFlags": 0 } ``` By packaging the full media and teaser preview in the `mediaIds` array and setting `fypFlags: 4`, the content is instantly optimized for the FYP algorithm, ensuring maximum discovery without opening a web browser. ## How to Build Tools and Develop Apps for Media Automation Solo operators do not need dedicated engineering departments to develop apps or implement efficient systems. Modern API access supports both scriptable logic and zero-code interfaces. ### The Native n8n Workflow (Zero-Code Platform Pipeline) According to the [Native Fansly n8n Setup and Workflows guide](/blog/fansly-n8n-integration), creators can utilize a native n8n node to construct a visual automation pipeline: 1. **Storage Trigger:** A creator drops exported video files into a designated Google Drive or Dropbox folder. 2. **Auto-FFmpeg Generation:** A cloud function slices a 5-second teaser clip from the master video. 3. **Fansly n8n Node Execution:** The n8n workflow initiates the upload of both files, monitors the `jobId` statuses, binds them into a single post template with `fypFlags: 4`, and schedules the publication for optimal traffic windows. ### Lightweight Python Watcher Daemon For technically inclined creators, a lightweight local script can monitor desktop rendering directories and interface directly with the REST endpoints to upload files and publish content. This completely replaces hours of manual overhead with a passive, background daemon. ## How the Fansly API Powers Creator-Economy SaaS As the creator economy matures in 2026, the underlying infrastructure is transitioning from basic point solutions to robust CRM and automation suites. The [Fansly API platform](/blog/fansly-api-integration-guide) provides a production-grade developer environment designed specifically to support agencies, developers, and SaaS founders. By offering over 200 live endpoints, granular permissions, and real-time HMAC-SHA256 signed webhooks, the Fansly API ensures that developers can program media operations, reconcile earnings, and manage customer service without relying on brittle, unofficial browser scraping extensions. Furthermore, the inclusion of webhook idempotency keys ensures zero-loss transaction tracking for subscriber purchases and tips—a critical feature for scaling a profitable creator business. ## Conclusion Automating the administrative burden of media publishing is the most effective way for solo operators to scale their digital presence in 2026. By utilizing developer endpoints to bypass manual browser workflows, creators can guarantee their content consistently hits FYP algorithmic requirements. Whether you decide to deploy no-code automation tools, script a lightweight Python daemon, or develop apps for broader agency use, taking control of API posts is the key to reclaiming hours of weekly productivity and focusing entirely on creative growth. --- # Automating Your Welcome Funnel on Fansly: Boost Day-One PPV Sales Canonical: https://www.fansly-api.com/blog/fansly-welcome-message-automation > Learn how to use no-code automation tools to build an effective Fansly welcome funnel that drives subscriber engagement and maximizes Day-One PPV sales. Keywords: no code, automation tools, no code development platforms, api automation Direct messaging on direct-to-consumer creator platforms is not just a customer service channel; it is the primary engine of monetization. Recent 2026 industry data reveals that high-performing accounts generate 40% to 60% of their gross earnings from pay-per-view (PPV) messaging and tips, maintaining an 8:1 to 9:1 DM-to-subscription revenue ratio according to [xcelerator Model Management](https://onlyfanscourse.com/blog/chatting-sales-master-guide/) and [Aurifan](https://aurifan.com/guides/dm-strategy-guide). However, there is a critical drop-off in user engagement: over 70% of new subscribers never initiate a DM conversation on their own. Waiting for incoming messages leads to immediate fan decay. By leveraging no-code solutions and modern automation tools to implement a structured welcome sequence, solo creators and agencies can capture high-intent subscribers immediately, significantly boosting Day-One PPV sales. ## What is an Automated Welcome Funnel? An automated welcome funnel is a pre-scheduled sequence of direct messages triggered automatically when a new fan subscribes, follows, or tips on a creator platform. Instead of manually responding to every new user, creators use automation to instantly send a personalized greeting, gauge the subscriber's preferences, and deliver targeted PPV media without active intervention. Automating a structured welcome sequence within the first 24 hours capitalizes on the highest-intent window in a subscriber's lifecycle. Implementing this system increases Day-1 subscriber reply rates from 15–25% to a staggering 50–65%, and lifts first-week Average Revenue Per Paying User (ARPPU) from under $15 to between $22 and $40, according to [xcelerator Model Management](https://onlyfanscourse.com/blog/retention-growth-how-to-write-a-welcome-flow-step-by-step/). ## The Critical Role of Speed-to-Lead in 2026 In creator DM funnels, response speed is the primary conversion lever. The [OnlyTraffic / xcelerator](https://onlyfanscourse.com/blog/chatting-sales-metrics-dashboard/) dashboard metrics show that response times under 5 minutes produce a 3.2x higher PPV conversion rate than responses delayed past 15 minutes. Here are the performance baselines of automated funnels versus manual operations: | Metric | Without Automated Funnel | With Structured Welcome Funnel | | :--------------------------- | :------------------------ | :------------------------------ | | **Day-1 DM Reply Rate** | 15% – 25% | **50% – 65%** | | **Day-3 PPV Purchase Rate** | 5% – 10% | **18% – 28%** | | **First-Week ARPPU** | $8.00 – $15.00 | **$22.00 – $40.00** | | **Welcome DM Open Rate** | \~40% (mass broadcasts) | **Up to 80% (personalized)** | Furthermore, [Sozee](https://www.sozee.ai/resources/fansly-messaging-guide/) reports a +28% subscriber retention lift when creators properly enforce DM locks and filtering combined with automated messaging. ## Anatomy of a High-Converting Welcome Sequence Top-performing creators structure their Day-1 welcome sequences around psychology rather than hard selling. Dumping a comprehensive price list immediately upon subscription often triggers buyer paralysis. Instead, use a multi-step approach. ### Phase 1: The Welcome DM (Hour 0) Establish immediate connection and prompt a micro-commitment reply. Set a natural delay (between 60 to 180 seconds) so the message feels organic. As noted in the [Fansly Creator Hub](https://creatorhub.fansly.com/messaging-2/), fans cannot distinguish between a mass, automated, or personal DM when delivered contextually. - **Optimal Framework:** Warm greeting, clear posting schedule overview, and a routing question. - **Expert Script Pattern:** *"Hey! Thanks so much for subscribing 💕 Quick question so I can send the right content your way: Are you here for (A) my daily casual lifestyle sets, or (B) exclusive custom video drops? Reply A or B and I’ll send you a special starting preview."* ([SlyKiwi](https://slykiwi.com/blog/what-to-send-in-a-fansly-welcome-message-p161/)) ### Phase 2: The Micro-PPV Teaser (Hour 6–12) Generate day-one cash flow with low purchase friction. Deliver an impulse-priced mini-set or behind-the-scenes vault item priced between $5 and $15, tailored to the tier or routing question they interacted with. ### Phase 3: The Engagement Check & Upsell (Hour 24–48) Re-engage fans who did not unlock the initial PPV. Use keyword-based tip triggers that allow subscribers to reply with commands (e.g., tipping with the keyword `MENU`) to receive automated descriptions and higher-tier pricing options. ## Step-by-Step Guide: Level 1 Native Zero-Code Setup Creators can deploy an automated Day-One PPV message directly inside the platform. This zero-code approach handles basic triggers without third-party tools. 1. Navigate to your **Creator Dashboard** and select **Automated Messages** ([Fansly Help Center](https://help.fansly.com/en/articles/10544427-setting-up-automated-messages)). 2. Click **Create New Automated Message**. 3. Select your trigger: **New Subscriber**, **Subscription renewal**, or **New Tip**. 4. Apply filters to target specific subscription tiers (e.g., $25 VIP tier vs. $5 entry tier). 5. Set a **delay** (e.g., 120 seconds) and a **cooldown period** to prevent duplicating messages to the same fan. 6. Attach vault media, configure your **locked text** or **locked media pricing**, and click **Create**. 7. To maximize inbox efficiency, go to **Settings > Messaging Permissions** and enforce DM thresholds (e.g., restricting messages to fans who have spent $50+ on PPV), a strategy proven to protect creator time while boosting retention. ## Step-by-Step Guide: Level 2 Advanced API Automation While native tooling excels at the initial greeting, scaling beyond a single message requires advanced API automation. Native tools cannot run conditional multi-day sequences (e.g., if a subscriber buys PPV in 6 hours, tag them as 'VIP'; if not, send a 20% discount at 24 hours). This is where integrating no-code development platforms (like Make or Zapier) with a dedicated developer infrastructure transforms operations. By utilizing [Fansly API](/), creators and agencies gain a production-grade interface that exposes 200+ live endpoints and real-time HMAC-signed webhooks. This bridges the gap between manual operations and enterprise-scale automation without requiring software engineers. ### Building the Workflow with No-Code Development Platforms Instead of running resource-heavy polling scripts, event-driven API automation uses real-time HTTP POST notifications. According to the [Fansly API Webhooks Guide](/blog/fansly-webhooks-guide), utilizing webhooks reduces credit expenditure by up to 1,000x compared to legacy API polling. 1. **Catch the Incoming Webhook:** Add a `Custom Webhook` module in Make or Zapier. Register this endpoint URL inside the [Fansly API Dashboard](/blog/fansly-api-integration-guide) and subscribe to the `subscription.created` and `sale.completed` events. 2. **Verify Security:** Ensure your workflow checks the `X-Fansly-Signature` header (HMAC-SHA256) and idempotency keys to prevent double execution ([Fansly API Integration Guide](/blog/fansly-api-integration-guide)). 3. **Execute Phase 1 (T+2 mins):** Trigger a POST request to the `/chats/message` endpoint via the [Fansly API](/) to send the personalized welcome message based on the fan's subscription tier. 4. **Execute Phase 2 (T+6 hours):** Introduce a delay module. Query if a `sale.completed` event was triggered by this specific subscriber ID. If no sale exists, trigger a targeted, locked PPV preview message. 5. **Execute Phase 3 (T+24 hours):** Route buyers into a creator CRM (like Notion or Airtable) tagged automatically as "High Intent," while non-buyers receive a relationship-building poll. Mastering your welcome sequence separates casual hobbyists from top-tier earners. Whether you rely on native dashboards or leverage no-code development platforms and API automation for dynamic targeting, commanding the first 24 hours of the subscriber journey is your most powerful tool for sustainable revenue growth. --- # How Solo Creators Use Fansly Free Trial Links to Track Promo ROI Canonical: https://www.fansly-api.com/blog/fansly-free-trial-links-roi > A guide on using native Fansly tools and API data to accurately measure conversion funnels and return on investment for creator promotional campaigns. Keywords: api software, api tools, api data, data api As the creator economy continues to mature in 2026, solo creators face an ongoing attribution blindspot. While promotional efforts across Reddit, X (formerly Twitter), and paid shoutouts drive significant traffic, standard third-party link shorteners fail to track actual revenue. External smart links can register raw clicks, but they lose visibility the moment a user enters a platform's paywall. To solve this, successful creators are abandoning vanity metrics and deploying native Fansly Free Trial Links. By combining native tracking with modern API software, creators can trace exact conversion funnels from a cold click to a paid rebill, allowing them to calculate precise Return on Investment (ROI) across every promotional campaign. ## The Attribution Challenge: Native vs. Third-Party Links Historically, solo creators relied on third-party link aggregators to distribute links across social channels. However, creator economy analysts note that these third-party routing methods create significant blind spots for subscription-based businesses. Third-party links suffer from three critical flaws: 1. **Webview and Cookie Stripping**: In-app browsers, such as Instagram or TikTok webviews, frequently strip referrer data and drop cross-site cookies, obscuring exactly where traffic originates ([Linkx.ee](https://linkx.ee/fansly-link-in-bio)). 2. **Zero Downstream Financial Visibility**: A basic shortener records a click, but cannot determine whether the click resulted in a free follow, an expired trial, a $15 pay-per-view (PPV) sale, or a recurring 6-month rebill ([Creators Spicy Tea](https://www.creatorsspicytea.co/tracking-links/)). 3. **Platform Moderation**: External redirect links are increasingly flagged or shadowbanned by Reddit spam filters and Instagram algorithms in 2026 ([QR Chameleon](https://qrchameleon.com/blog/link-in-bio-onlyfans-fansly/)). Unlike external aggregators, Fansly's native architecture monitors top-of-funnel clicks, mandatory card verification, in-trial PPV monetization, and rebill conversions entirely within the platform's ecosystem. ## What Are Fansly Tracking and Gift Links? Fansly provides two interconnected native mechanisms for campaign tracking: Tracking Links and Subscription Discounts (Gift Links). ### Subscription Discounts (Gift Links) In Fansly's architecture, free trials and promotional discounts are configured as subscription discounts, often labeled as "Gift Links" in the interface and detailed in the [Fansly API Documentation](https://docs.onlyfansapi.com/api-reference/fansly/subscription-discounts/list-subscription-discounts). Creators can set the promotional price to $0.00 for a true free trial or offer a discounted initial rate. Crucially, creators can set a maximum claim ceiling (e.g., 50 claims) to create urgency and limit liability. The most valuable aspect of Fansly's native trial system is mandatory payment verification. The system requires users claiming a free trial to add a valid credit card on file ([BlackHatWorld Discussion](https://www.blackhatworld.com/seo/tracking-links-on-fansly.1645225/)). This critical friction point filters out scrape bots and non-spending lurkers, separating tire-kickers from high-intent subscribers. ### Native Tracking Links Fansly's dedicated tracking links feature allows creators to isolate traffic channels by generating unique URLs mapped to specific campaigns (e.g., `fansly.com/creator?r=reddit_gothic`). The system monitors daily metrics over custom date ranges, tracking clicks, claims, follows, and subscriptions natively ([OnlyFansAPI / Fansly Scribe Docs](https://docs.onlyfansapi.com/api-reference/fansly/tracking-links/get-tracking-link-stats)). ## Step-by-Step Guide: Tracking Promo ROI by Channel Solo creators apply native links across their main acquisition funnels to benchmark channel performance and redirect their marketing budget toward profitable sources. ### 1. Reddit Content Attribution Reddit remains a high-volume organic discovery engine, but audience intent varies wildly across communities. Generate a dedicated Free Trial Link for each primary subreddit category. Track the Click-to-Claim and Claim-to-Rebill ratios. A subreddit driving 800 clicks but only 3 claims signals low intent, while a niche subreddit driving 40 clicks but 15 claims reveals where daily posting efforts should be prioritized. ### 2. Paid Shoutouts and Creator Collabs Paid shoutouts often cost between $50 and $500 per placement. Without attribution, creators have no way of knowing whether a partner delivered genuine paying fans or inactive bot clicks ([OnlyX Agency](https://onlyxagency.com/onlyfans-promotion-services)). By issuing a custom, capped Free Trial Link exclusively to the shoutout partner, a creator can verify exact ROI. If a $100 shoutout yields 30 claims, 6 regular rebills at $12/month, and $45 in first-week PPV tips, the creator instantly validates a positive return. ### 3. Organic Social Bio Links Instead of putting a raw, unmonitored link on X (Twitter) or routing through restrictive link trees, creators use dedicated tracking links with customized trial offers in their bios. Monitoring these tracking link stats daily alerts creators to platform shadowbans or reach throttling before it significantly impacts monthly revenue. ## How to Calculate Promo Conversion and True ROI To make strategic decisions, evaluate these four core metrics: - **Claim Rate (%)**: (Trial Claims / Unique Link Clicks) x 100 - **Paid Rebill Conversion Rate (%)**: (Paid Renewals at End of Trial / Total Trial Claims) x 100 - **30-Day Cohort Revenue**: Rebills + In-Trial PPV Sales + Attributed Tips - **Promo ROI (%)**: ((30-Day Cohort Revenue - Promotional Cost) / Promotional Cost) x 100 According to recent performance data, free trial claim-to-rebill conversions average between 8% and 18% for broad social traffic ([Infloww Blog](https://infloww.com/blog/fansly-analytics-101)). However, high-affinity creator cross-promotions frequently see conversion rates between 20% and 32%. Furthermore, top creators generate 35% to 60% of their total campaign revenue during the trial window itself through automated PPV teasers ([Creator Hero](https://www.creatorhero.com/blog/fansly-vs-onlyfans-the-ultimate-platform-showdown)). ## Scaling Attribution: Leveraging API Tools and Webhooks While native links solve the attribution problem inside the user interface, scaling past $5,000 to $10,000 per month introduces operational friction. Manually checking multiple links, matching subscriber IDs to renewal logs, and calculating spreadsheet ROI costs professional creators dozens of hours each month ([Fansly API Blog](/ai-financial-analytics)). To eliminate this manual labor, professional creators and management agencies rely on modern API tools and robust API software to automate the data workflow entirely. By connecting to a developer-grade integration platform like the [Fansly API](/), agencies can access over 200 live endpoints. Instead of manual dashboard exports, automated API data queries programmatically pull active campaign URLs, click statistics, and gift link utilization. ### Real-Time Conversion Workflows Rather than relying on manual polling, the [Fansly API Integration Suite](/blog/fansly-api-integration-guide) delivers HMAC-SHA256-signed webhooks directly to external automation services: - **subscription.renewed**: Fires the instant a trial user's card successfully clears the Day-30 renewal charge, tying revenue back to the originating campaign link. - **sale.completed**: Captures PPV purchases made by trial subscribers during their free period. Using platforms like n8n, Make, or Zapier, non-technical creators can link their data API directly to Google Sheets, external CRMs, or Airtable. When a free trial claim converts, the workflow logs the customer acquisition cost (CAC) and customer lifetime value (LTV). If an attribution link underperforms, the automated sequence can disable the discount link and alert the creator to reallocate their marketing budget. ## Moving Beyond Vanity Metrics In today's highly competitive creator economy, clicks are merely vanity metrics; credit card-verified claims and 30-day rebills are the only valid measurements of campaign success. By combining Fansly's native tracking capabilities with programmatic API software, solo creators can operate with the operational precision and revenue attribution of a venture-backed e-commerce brand. --- # The Solo Creator’s Guide to Automating Fansly: Save 20 Hours a Week Canonical: https://www.fansly-api.com/blog/fansly-automation-for-creators > A comprehensive guide for solo creators on leveraging API automation and no-code tools to streamline operations and increase revenue. Keywords: build app no code, no code, automation tools, api automation In 2026, the creator economy has reached an estimated valuation of $248.95 billion, yet solo creators scaling their subscription businesses continue to hit a severe operational ceiling. Industry data compiled by [SirenCY](https://www.sirency.com/blog/onlyfans-business-scaling-team-building-hiring-2026) reveals that creators earning between $5,000 and $15,000 per month frequently work 60 to 80 hours a week, with up to 40 of those hours consumed entirely by direct messaging, fan upsells, and administrative tasks. Because direct messaging accounts for nearly 70% of subscription platform revenue, inbox responsiveness directly governs creator income. To survive, many turn to management agencies, sacrificing huge portions of their revenue. Today, however, the emergence of modern **automation tools** and visual logic platforms allows solo creators to reclaim 20+ hours a week and retain 100% of their earnings. ## What is Fansly Automation? Fansly automation is the process of using software to programmatically handle repetitive fan interactions—such as welcome messages, tip acknowledgments, and lapsed subscriber check-ins—without manual intervention. While native platform tools offer basic automated replies, true operational scale requires **API automation**. By connecting a platform account to external visual logic workflows, creators can execute complex, multi-step sequences that adapt to subscriber behavior in real time, matching the 24/7 responsiveness of a full-time chat agency. ## The Creator's Dilemma: Agencies vs. Independent Automation When a solo creator hits the time ceiling, standard industry advice often points toward hiring an agency or third-party chatting contractor. However, the financial and operational trade-offs of this route are steep. Full-service management agencies typically extract 30% to 50% of gross earnings, frequently before the platform's own 20% commission is deducted ([FansAgent](https://fansagent.com/blog/fansly-agency-fees-vs-software)). This model severely impacts take-home pay. According to [Aruna Talent](https://arunatalent.com/blog/how-much-does-an-onlyfans-agency-cost/), on an account generating $10,000 in monthly gross revenue, the creator often keeps as little as $3,000 to $5,000. Beyond financial drain, agency arrangements introduce significant risks: - **Brand Voice Dilution:** Outsourced chatters can misrepresent the creator’s tone, alienating core fans. - **Restrictive Contracts:** Standard agreements often lock creators in for 6 to 12 months with aggressive non-competes ([OFMODEL Agency](https://ofmodel.agency/how-much-do-onlyfans-agencies-take/)). - **Security Vulnerabilities:** Handing raw account passwords to off-shore teams exposes creators to credential leaks and data exports. In contrast, deploying **no-code** software solutions requires a flat, predictable monthly fee, allowing creators to keep all of their net earnings while maintaining absolute control over their brand and data. ## 3 Essential Automation Workflows to Reclaim 20 Hours a Week Solo creators can replicate the throughput of an entire chat team by establishing three core automated flows. ### 1. Automated Welcome Messages and Tier Onboarding Manually welcoming new subscribers and explaining custom menus drains 5 to 7 hours a week. Instead, creators can use real-time webhook triggers to instantly deliver a dynamic introductory DM containing tier-specific benefits and pinned pay-per-view (PPV) teasers. Adding a humanizing delay (e.g., 45 to 120 seconds) ensures the message feels organic. As noted in the [Fansly Help Center](https://help.fansly.com/en/articles/10544427-setting-up-automated-messages), these automated messages can include media bundles and locked text without cluttering the creator's active DM list. ### 2. Dynamic Tip Gratitude and "Whale" Alerts Parsing tip notifications and sending promised locked content manually takes 6 to 8 hours weekly. Automated routing can parse tip receipts instantly. If a tip matches a specific keyword or amount (e.g., "$25 for video access"), the automation unlocks and sends the content immediately. For high-value spenders (tips over $50 or $100), the system can push an instant "Whale Alert" to the creator's private Telegram or Discord. This allows the creator to jump in personally while the subscriber is still online and highly engaged. ### 3. Expired Fan Check-Ins and Churn Mitigation Identifying lapsed subscribers and sending winback notes is a tedious manual process. When a subscriber fails to renew, an automated winback journey can trigger automatically: - **Day 1 Post-Expiration:** A friendly check-in message thanking them for their past support. - **Day 7 Post-Expiration:** A preview trailer of upcoming content and an exclusive renewal discount. This background flow consistently recovers 10% to 20% of lapsed fans without any manual data exporting. ## How to Set Up Your Automation Stack While native platform tools handle basic tasks, they lack multi-step logic, multi-channel notifications, and external CRM syncing. To build enterprise-grade workflows, solo creators rely on dedicated developer platforms to bridge their accounts with external logic builders. ### Step 1: Connect to a Provider Platform The foundation of modern creator tooling is the [Fansly API](/). This production-grade developer platform exposes over 200 live endpoints and real-time HMAC webhooks. By utilizing native webhooks over traditional polling models, event notifications execute instantaneously—closing the critical latency gap between when a fan tips and when engagement occurs ([Fansly API Webhooks Guide](/blog/fansly-webhooks-guide)). ### Step 2: Integrate Your Logic Engine Using the platform's secure API key, connect your account to visual logic builders like Make.com, Zapier, or n8n. Because of pre-configured modules, creators can establish complex scenarios in minutes without writing a single line of code ([Fansly API No-Code](/no-code)). ### Step 3: Deploy Workflows and Sync CRM Data You can essentially **build an app with no-code** visual interfaces to run your entire backend. Route every subscriber event and completed sale to an external database (like Airtable, Google Sheets, or Notion). This instantly creates a living CRM that tracks cohort lifetime value (LTV), popular pricing tiers, and retention drop-offs, giving you professional business analytics on autopilot. ## Time Savings Breakdown Transitioning from manual DM handling to event-driven logic yields immediate lifestyle and business benefits. | Operational Task | Manual Time Spent | Automated Solution | Time Reclaimed | | :------------------------------- | :------------------ | :-------------------------------------- | :------------------ | | New Subscriber Welcomes | 5–7 hrs/week | Webhook-triggered onboarding DM | 5–7 hrs/week | | Tip Gratitude & Fulfillment | 6–8 hrs/week | Keyword/amount auto-reply & unlock | 5–7 hrs/week | | High-Roller Engagement | 3–5 hrs/week | Real-time Telegram alerts | 2–3 hrs/week | | Expired Fan Re-Engagement | 4–6 hrs/week | Automated 3-day/7-day winback | 4–5 hrs/week | | Reporting & Data Entry | 3–4 hrs/week | Real-time sync to external CRM | 3 hrs/week | | **Total Weekly Savings** | **21–30 hrs/week** | **Event-Driven Workflow Stack** | **\~20+ hrs/week** | ## Conclusion The modern solo creator does not need to forfeit massive equity percentages to scale their business. By utilizing **API automation** and robust visual logic platforms, creators can systematically eliminate 20 hours of administrative busywork per week. Adopting these technologies transforms a grueling 24/7 grind into a highly efficient, automated digital business that retains 100% of its hard-earned revenue. --- # Fansly MCP Server: Technical Architecture and Multi-Account Integration Guide Canonical: https://www.fansly-api.com/blog/fansly-mcp-server-guide > A deep dive into the technical architecture of the Fansly MCP server and how developers can utilize it for secure, scalable multi-account AI agent integration. Keywords: api ai, ai for developers, api documentation, api endpoints, api tools Building autonomous AI agents to manage creator-economy workflows requires overcoming strict infrastructure constraints: context window conservation, tenant data isolation, and proxy affinity. When building robust API AI systems for agency environments, relying on fragile browser automations or exposing raw session cookies often leads to account lockouts and hallucination. To solve this, [Fansly API](/) has deployed a production-grade Model Context Protocol (MCP) server. By implementing the open MCP standard, the platform bridges the gap between Large Language Model (LLM) applications and external runtime environments, offering a standardized pathway to safely orchestrate creator accounts at scale. This guide details the technical architecture of the Fansly MCP Server, providing step-by-step integration mechanics for single-endpoint query routing, multi-tenant proxy management, and token authentication. ## What is the Fansly MCP Server? The Fansly MCP Server is a highly available gateway control plane that standardizes bidirectional communication between AI agent runtimes (like Claude Desktop, Cursor, or custom LangGraph swarms) and the Fansly creator platform. It translates over 200 live platform REST API endpoints into 80+ model-controlled MCP tools. Operating via JSON-RPC 2.0 over Streamable HTTP (Server-Sent Events) or standard input/output (stdio), the server acts as an intelligent intermediary. It ensures AI agents never touch raw user credentials while maintaining strict tenant isolation across thousands of creator accounts via dedicated mobile proxy pools. ## Single-Endpoint Routing Mechanics: `?platforms=fansly` Exposing an entire monolithic catalog of API tools to an AI model creates severe context overhead. An agent orchestrating a Fansly fan renewal campaign does not need OnlyFans schemas flooding its context window. Fansly API solves this dynamic namespace challenge via URL-based capability negotiation. By appending dynamic routing parameters to the public MCP gateway, developers ensure the AI client only receives context-optimized schemas: ```http https://app.onlyfansapi.com/mcp/onlyfans-mcp?platforms=fansly ``` When an AI client establishes a session using this endpoint, the server filters the global tool dictionary. It returns only the curated `fansly_` tools, reducing prompt token consumption by over 60% compared to unified creator server implementations. For hybrid agencies, the query string supports comma-delimited composability (e.g., `?platforms=fansly,onlyfans`), maintaining strict namespace isolation. ## Exploring the 80+ Granular `fansly_` Tool Schemas The Fansly MCP server maps complex [API endpoints](/blog/fansly-api-integration-guide) into granular, schema-enforced MCP tools. These tools feature strict parameter typing and declarative boundaries, categorized into several functional domains: - **Subscriber CRM & Whale Analytics:** Tools like `fansly_get_fan_profile` and `fansly_list_whales`. According to [Fansly AI Fan Analytics](/ai-fan-analytics), approximately 10% of creator subscribers generate 80% of platform revenue. These tools allow agents to rapidly isolate top spenders based on Lifetime Value (LTV) or 30-day tip velocity. - **Direct Messaging & Mass Comms:** Tools like `fansly_send_message` orchestrate 1-to-1 conversational selling, Pay-Per-View (PPV) attachments, and scheduling. - **Content Vault Management:** Tools including `fansly_upload_media` and `fansly_create_post` handle PPV publishing and media archiving. - **Financial Tracking:** Tools like `fansly_get_earnings_summary` track gross merchandise value (GMV), renewals, and manual tips. ## Multi-Account Architecture: The `fansly_acct_` Routing Engine For enterprise agencies managing dozens of talent profiles, spinning up separate MCP server instances per creator exhausts host memory and fragments configuration files. The multi-account routing engine resolves this through a single-key multi-tenant paradigm. A single master organization API token maps to an agency's entire roster. Specific routing is explicitly handled at the invocation level via the `fansly_acct_` parameter. When an agent invokes a tool, it passes the target account identifier: ```json { "jsonrpc": "2.0", "id": 42, "method": "tools/call", "params": { "name": "fansly_get_fan_profile", "arguments": { "account_id": "fansly_acct_8f0a29b4e1", "fan_id": "user_992104" } } } ``` Behind the gateway, each `fansly_acct_` instance is bound to a dedicated, persistent mobile/residential IP address. Session tokens, CSRF tokens, and proxy routes are encapsulated in memory stores indexed by the `account_id`, preventing cross-tenant data leakage and platform-level IP correlation. ## Authentication, Security, and Production Safeguards Operating autonomous agents over commercial profiles requires stringent defense-in-depth protocols to prevent accidental broadcasts or credential exposure. ### Bearer Token Provisioning Communication requires an organization master key passed via HTTP Authorization headers (e.g., `Authorization: Bearer fa_live_9a8b7c...`). The LLM runtime never sees the underlying Fansly platform passwords or 2FA seeds. ### Granular Write Safeguards Following [Model Context Protocol safety recommendations](https://modelcontextprotocol.io/specification/2026-07-28/server/tools), the server mounts in read-only mode by default. Write operations (`fansly_send_message`, `fansly_create_post`) return dry-run validations unless the client environment explicitly sets `FANSLY_MCP_ENABLE_WRITES=1`. Furthermore, human-in-the-loop elicitation flows prompt human operators before dispatching high-impact financial transactions. ### Webhook Synchronization Over Polling Traditional integrations rely on cron polling to detect incoming messages, which drains request limits rapidly. As detailed in the [Fansly Webhooks Guide](/blog/fansly-webhooks-guide), cron polling 20 accounts consumes over 28,800 API calls daily. The MCP architecture leverages HMAC-SHA256 signed webhooks to trigger orchestration agents instantly, cutting operational costs by orders of magnitude while responding to fan actions in seconds. ## Step-by-Step Implementation Guide Integrating AI for developers into agency tooling is highly standardized using the [Model Context Protocol Specification](https://modelcontextprotocol.io/specification/2026-07-28/basic/index). Below are configurations for the most common development environments in 2026. ### 1. Claude Desktop Integration Add the remote streamable HTTP setup to your `claude_desktop_config.json` file: ```json { "mcpServers": { "fansly": { "url": "https://app.onlyfansapi.com/mcp/onlyfans-mcp?platforms=fansly", "headers": { "Authorization": "Bearer fa_live_your_agency_master_key" } } } } ``` ### 2. IDE Configuration (Cursor / Windsurf) To leverage contextual AI natively within your IDE while developing custom CRM modules, update your workspace configuration. For Cursor (`.cursor/mcp.json`): ```json { "mcpServers": { "fansly-agency": { "type": "sse", "url": "https://app.onlyfansapi.com/mcp/onlyfans-mcp?platforms=fansly", "headers": { "Authorization": "Bearer fa_live_your_agency_master_key" } } } } ``` ### 3. Autonomous Python Agent (LangGraph / CrewAI) For orchestration swarms, utilize the official MCP Python SDK: ```python import asyncio import os from mcp import ClientSession from mcp.client.sse import sse_client async def run_fansly_crm_agent(): server_url = "https://app.onlyfansapi.com/mcp/onlyfans-mcp?platforms=fansly" headers = {"Authorization": f"Bearer {os.environ['FANSLY_API_KEY']}"} async with sse_client(server_url, headers=headers) as (read_stream, write_stream): async with ClientSession(read_stream, write_stream) as session: await session.initialize() # Discover tools and execute a targeted whale query result = await session.call_tool( name="fansly_list_whales", arguments={ "account_id": "fansly_acct_prod_creator_01", "metric": "30d_velocity", "min_spend_usd": 250.0, "limit": 5 } ) print("Top spenders identified:", result.content[0].text) if __name__ == "__main__": asyncio.run(run_fansly_crm_agent()) ``` ## Operational Best Practices Successfully deploying autonomous operations demands adherence to established architectural standards and API documentation rules: - **Context Window Strategy:** Avoid passing massive raw chat histories to the LLM. Instead, invoke intermediate tools like `fansly_get_fan_summary` to yield concise 200-word behavioral summaries, reserving tokens for complex reasoning tasks. - **Rate Limit Budgeting:** Referencing the official [Fansly API Pricing & Scale Tiers](/pricing), infrastructure capacity scales based on tier. Basic plans permit 1,000 requests per minute (RPM) across 1-2 accounts, while Pro configurations support 5,000 RPM across 5+ accounts. - **Idempotency:** Include an `idempotency_key` parameter when invoking write operations (like `fansly_send_message`). If network drops occur, re-transmissions are safely deduplicated by the gateway, preventing double-billing to users. By leveraging the Fansly MCP Server, engineering teams bypass the fragility of reverse-engineered scripts, securing an event-driven, token-efficient, and multi-tenant foundation for modern creator agency automation. --- # Why Python Scrapers Fail on Fansly: The Case for a Hosted REST API Canonical: https://www.fansly-api.com/blog/fansly-scraper-vs-api > An analysis of why custom scrapers fail against modern bot detection and the advantages of using a professional REST API integration. Keywords: developer s, api security, api scraper, api authentication For software developers building creator management tools, automated messaging platforms, and financial analytics dashboards in 2026, data extraction is a foundational hurdle. Engineering teams frequently start with custom Python automation using standard networking libraries. However, within days or weeks of deployment, these internal pipelines inevitably degrade. Requests trigger `403 Forbidden` errors, proxy budgets balloon, and creator accounts face rate-limiting or administrative termination due to anomalous traffic patterns. Modern creator platforms rely on layered enterprise bot defenses—specifically Cloudflare Bot Management featuring JA4 TLS fingerprinting, HTTP/2 SETTINGS frame analysis, and dynamic Turnstile challenges. This technical breakdown compares the deteriorating viability of in-house automation against the industry-standard architecture: integrating an enterprise hosted REST platform. ## What is the Architectural Divide in Creator Platform Integration? The architectural divide in creator-economy automation centers on how data is retrieved and how sessions are managed. On one side is the traditional **custom automation stack**. This involves developers stringing together libraries like `requests`, `httpx`, `Playwright`, or `Selenium` to emulate human browser sessions. It requires rotating residential proxies, solving CAPTCHAs, and repeatedly polling endpoints to detect changes. On the other side is the **hosted REST API model**. Rather than fighting the platform's perimeter security, this approach utilizes a centralized, enterprise-grade gateway—such as [Fansly API](/)—that maintains stable underlying connections. Developers interact strictly with standardized JSON endpoints and rely on event-driven webhooks, entirely removing the need for browser emulation and continuous polling. ## The Technical Anatomy of Scraper Failure To understand why a custom-built API scraper collapses, engineers must inspect how modern anti-bot systems evaluate inbound traffic. Traffic is evaluated across a multi-tier defense hierarchy before origin endpoints ever process incoming requests. ### Layer 1: TLS Fingerprinting (JA3 vs. JA4) During the initial HTTPS handshake, a client broadcasts its supported cipher suites, extensions, and signature algorithms. Standard Python network stacks rely on system OpenSSL, whereas modern Chromium browsers use BoringSSL. According to [Zyte's security research](https://www.zyte.com/learn/why-python-requests-gets-403-forbidden/), OpenSSL lacks GREASE (Generate Random Extensions And Sustain Extensibility), a feature Google Chrome uses to inject randomized dummy values to prevent protocol ossification. Furthermore, Cloudflare evaluates these handshakes using the [JA4 fingerprint standard](https://developers.cloudflare.com/bots/additional-configurations/ja3-ja4-fingerprint/). As noted in [Krowdev's 2026 bot detection analysis](https://krowdev.com/article/bot-detection-2026/), Chrome on TLS 1.3 produces a specific signature (`t13d1516h2`), while Python stacks emit low-entropy signatures that edge WAFs instantly score as malicious bots. ### Layer 2: HTTP/2 Transport Signatures If a scraper bypasses TLS checks, it immediately encounters HTTP/2 transport-layer verification. The [BrowserInsight Akamai Fingerprint Breakdown](https://browserinsight.net/blog/http2-fingerprinting) reveals that anti-bot systems evaluate deterministic factors such as explicit SETTINGS parameters, window update increments, and pseudo-header order. Modern browsers transmit HTTP/2 pseudo-headers in a rigid sequence (`:method`, `:authority`, `:scheme`, `:path`). As documented in [Crawlex's 2026 HTTP/2 guide](https://blog.crawlex.net/blog/http2-fingerprinting-akamai-format/), custom libraries frequently reorder these or insert custom pseudo-headers, resulting in an immediate `403 Forbidden` response. ### Layer 3: Cloudflare Turnstile & Managed Challenges When traffic yields an ambiguous bot score, platforms trigger Cloudflare Turnstile. According to a [2026 deep dive on Turnstile internals by ProxyHat](https://proxyhat.com/blog/cloudflare-turnstile-internals-2026), this involves an adaptive Proof-of-Work (PoW) that forces the client to iterate SHA-256 hashes. Crucially, Turnstile issues a `cf_clearance` cookie that is cryptographically pinned to the exact client TLS characteristics, IP address, and User-Agent. Exporting this cookie from a headless browser to a Python worker fails because the network profiles do not match. ## Architecture Comparison: Custom Automation vs. Hosted REST API Engineering leaders often treat in-house automation as a low-cost endeavor, but the total cost of ownership shifts drastically after deployment. Here is how custom infrastructure compares to an enterprise integration platform. | Architectural Dimension | Custom Python Automation Stack | Enterprise Hosted REST Platform | | :------------------------ | :--------------------------------------------------------------------------------- | :----------------------------------------------------------------- | | **Protocol Emulation** | Requires continuous patching of BoringSSL, JA4 hashes, and HTTP/2 frames. | Handled entirely upstream by dedicated infrastructure engineers. | | **Anti-Bot Navigation** | Mandates headless browser farms, CAPTCHA solver APIs, and rotating IPs. | Abstracted completely; zero browser automation required. | | **Data Synchronization** | Inefficient cron polling (e.g., polling every 60 seconds) leading to rate limits. | Sub-second, real-time push delivery via HMAC-SHA256 webhooks. | | **Account Ban Risk** | High; abnormal behavioral patterns and proxy IP leaks trigger platform bans. | Proven zero-ban history across 5,000+ connected creator accounts. | ## The Inefficiencies of Polling vs. Real-Time Webhooks A core vulnerability of custom architectures is the reliance on polling. To detect incoming messages, tips, or subscriptions, a script must repeatedly ping platform endpoints. As outlined in the [Fansly API Webhooks Guide](/blog/fansly-webhooks-guide), polling creates compounding infrastructure costs and high latency windows. Polling an endpoint every 60 seconds across 20 creator accounts generates 28,800 requests daily—consuming massive bandwidth just to confirm no new events occurred. Modern integration architecture replaces polling with push notifications. Event-driven architectures deliver structured payloads within milliseconds of the event occurring. To guarantee strict API security, these webhook deliveries include a cryptographic signature (e.g., an `X-Fansly-Signature` header) that consuming applications validate using HMAC-SHA256, completely preventing replay attacks and payload tampering. ## Total Cost of Ownership and API Authentication Research into scraping infrastructure by [Import.io](https://www.import.io/post/the-hidden-cost-of-web-scraping-why-data-teams-are-moving-to-market-intelligence-platforms) highlights that hidden costs quickly overwhelm engineering budgets. Maintaining custom bypasses requires residential proxy networks (averaging $8 to $15 per gigabyte), third-party CAPTCHA solvers, and 10 to 20 hours per month diagnosing shifting JSON schemas and `m3u8` video segment mutations (a frequent failure point documented in open-source repositories like [Fansly Downloader Issue #23](https://github.com/prof79/fansly-downloader-ng/issues/23)). More importantly, bypassing native login flows creates existential risk to the creator's account. Transitioning to a hosted architecture standardizes API authentication. Instead of juggling fragile session cookies and rotating proxy pools, developers authenticate via standard Bearer tokens. Modern agencies and SaaS providers implement [Fansly API](/) to bypass the maintenance treadmill entirely. With over 200 live endpoints and native integrations for tools like n8n and Zapier, operations teams can configure automated whale-tipping alerts and CRM synchronization workflows without writing reverse-engineering code. ## Final Verdict The era of maintaining custom automation against enterprise Cloudflare-protected creator platforms has effectively ended in 2026. With edge platforms enforcing deep-packet TLS inspection, HTTP/2 framing consistency, and dynamic cryptographic challenges, DIY scrapers present an unmanageable maintenance burden. For developers and CRM architects, abandoning the break-fix cycle of fragile scripts in favor of a dedicated enterprise REST service delivers guaranteed uptime and protocol-level compliance. Transitioning to standard API authentication and real-time HMAC webhooks frees engineering teams to focus on building core product value rather than perpetually fighting adversarial anti-bot defenses. --- # Fansly API Quickstart: Authentication, Endpoints, and HMAC Webhook Verification Canonical: https://www.fansly-api.com/blog/fansly-api-quickstart > A developer-focused guide on utilizing the Fansly API, covering secure authentication, endpoint management, and real-time webhook verification. Keywords: api keys, api documentation, api endpoints, api authentication, real time api The creator economy has transitioned from isolated social media profiles into high-throughput digital enterprises. On platforms hosting upwards of 130 million registered users, managing multiple creator accounts manually or via fragile reverse-engineered scraping scripts is no longer a viable strategy for agencies and enterprise tooling providers. This quickstart guide serves as comprehensive API documentation for developers looking to build scalable CRMs, mass-messaging tools, and revenue dashboards. Whether you are integrating natively or using workflow orchestrators, understanding how to manage API keys, process integer-based currency formats, and securely verify real-time API webhooks is critical for a production-grade deployment. ## What is the Fansly API? The [Fansly API](/) is an enterprise-grade developer platform engineered by Fans Holdings OÜ that replaces headless browser automation with official, stable infrastructure. Built for creator management agencies and SaaS platforms, it exposes over 200 live REST API endpoints covering messaging, CRM profiles, transactions, and media vaults. With a production track record of supporting over 5,000 connected creator accounts and processing more than 150 million requests with zero platform bans, the Fansly API provides a secure environment for account scaling. It also features a real-time push architecture via cryptographically signed webhooks, eliminating the credit-intensive need for continuous polling. ## Step 1: API Authentication and Key Management Secure API authentication is the foundation of your integration. The platform utilizes bearer token authentication, which requires developers to pass a secure token in the HTTP headers of every request. ### Generating and Scoping API Keys To interact with the platform, you must authenticate your HTTP clients using API keys generated from your developer dashboard. According to the [Fansly API Integration Guide](/blog/fansly-api-integration-guide), you should follow these steps: 1. **Register an Account:** Create an account on the [Fansly API](/) platform. New developers receive a sandbox allocation of 10 free credits to test live connections. 2. **Create an API Key:** Open [app.onlyfansapi.com/api-keys](https://app.onlyfansapi.com/api-keys) and generate a key. Keys are not scoped: every key can call every endpoint for every account connected to your team, so create one key per integration and rotate any key you hand to an external developer. 3. **Secure Your Secrets:** Store your API keys in a secure runtime environment, such as AWS Secrets Manager or encrypted `.env` files. Never commit them to public version control. ### Standard Request Headers Every inbound request requires specific HTTP headers to define the payload type, authenticate the client, and target specific creator accounts. | Header Name | Example | Requirement | Description | | :--------------- | :-------------------------- | :----------------------- | :----------------------------------------------- | | `Authorization` | `Bearer YOUR_API_KEY` | **Required** | Your developer platform secret API key. | | `Content-Type` | `application/json` | **Required** (POST/PUT) | Declares JSON formatting for payloads. | | `Accept` | `application/json` | **Required** | Ensures responses are returned as JSON. | **cURL Authentication Example:** ```bash curl -X GET "https://app.onlyfansapi.com/api/fansly/fansly_acct_XXXXXXXXXXXXXXX/chats" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Accept: application/json" ``` ## Step 2: Navigating Core API Endpoints Once authenticated, developers gain access to over 200 live API endpoints spanning six primary resource domains. These endpoints allow you to orchestrate complex agency workflows programmatically. - **Accounts & Sessions:** Endpoints like `/api/v1/accounts` connect creator accounts via 2FA and inspect proxy session health. - **Messaging:** Use `/api/v1/chats` and `/api/v1/messages/mass` to read direct messages, execute real-time chatbot replies, or queue bulk PPV blasts. - **Fans & CRM:** Query fan spend histories, subscription dates, and engagement tiers via `/api/v1/fans`. - **Financials:** Reconcile gross revenue, platform cuts, net payouts, and tracking link conversions using `/api/v1/earnings/summary`. - **Media & Vault:** Upload multimedia files (up to 1GB via remote URL) and publish tier-locked feed posts through `/api/v1/vault/media`. ## Step 3: Financial Data Integrity (The Millidollar Format) A common integration pitfall in creator-economy platforms is the mishandling of currency. Standard IEEE 754 floating-point operations (like `0.1 + 0.2` in JavaScript) introduce precision drift, which compounds into material accounting errors over thousands of PPV unlocks and tips. To ensure financial data integrity, Fansly represents currency in **thousandths of a dollar (millidollars)**. - $1.00 USD = 1000 - $5.00 USD = 5000 - $15.50 USD = 15500 - $0.05 USD (5 cents) = 50 ### TypeScript Conversion Example When building dashboards, always round your conversions to avoid intermediate representation anomalies: ```typescript export class FanslyCurrency { public static toMillidollars(dollars: number | string): number { const parsed = typeof dollars === 'string' ? parseFloat(dollars) : dollars; if (isNaN(parsed) || !isFinite(parsed)) throw new TypeError('Invalid amount'); return Math.round(parsed * 1000); } public static toFormattedUSD(millidollars: number): string { return new Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD', }).format(millidollars / 1000); } } ``` ## Step 4: HTTP Status Codes and Error Handling The platform complies with standard RFC 7231 HTTP response codes. According to [Fansly API Pricing and RPM Architecture](/pricing), handling rate limits (`429`) is especially critical depending on your plan tier (1,000 RPM for Basic vs. 5,000 RPM for Pro). | HTTP Code | Error Code | Recommended Recovery Action | | :--------- | :-------------------------- | :----------------------------------------------------------- | | **400** | `INVALID_PAYLOAD` | Validate payload against endpoint schema. | | **401** | `UNAUTHORIZED` | Verify `Authorization: Bearer ` header. | | **403** | `INSUFFICIENT_PERMISSIONS` | Re-issue API key with correct scopes via the dashboard. | | **429** | `RATE_LIMIT_EXCEEDED` | Honor `Retry-After` header; implement exponential backoff. | | **500** | `INTERNAL_UPSTREAM_ERROR` | Log `request_id` and open automated escalation via support. | ## Step 5: Implementing a Real-Time API with HMAC Webhooks Transitioning from continuous polling to a real-time API push architecture yields dramatic financial and performance advantages. According to the [Fansly Webhooks Guide](/blog/fansly-webhooks-guide), polling an active 20-creator roster once a minute burns roughly 28,800 credits daily. Conversely, webhooks cost just 1 credit per 100 events and deliver data within sub-second latencies. ### Webhook Security and Signature Verification When a webhook event (like `tip.received` or `message.received`) fires, the payload is sent via a POST request to your registered HTTPS URL. To prove the event originated from Fansly, it includes an `X-Fansly-Signature` header computed via HMAC-SHA256. **Security Mandate:** You must evaluate the HMAC hash against the raw, unparsed string buffer of the request body. Furthermore, to prevent timing attacks as outlined in [RFC 2104](https://datatracker.ietf.org/doc/html/rfc2104), comparisons must run in constant time. ### Node.js / Express Verification Reference ```typescript import express, { Request, Response } from 'express'; import { createHmac, timingSafeEqual } from 'crypto'; const app = express(); // Capture raw body buffer for verification app.use(express.json({ verify: (req: any, _res, buf) => { req.rawBody = buf; } })); const WEBHOOK_SECRET = process.env.FANSLY_WEBHOOK_SECRET; const processedEvents = new Set(); app.post('/api/fansly/webhook', (req: Request, res: Response): any => { const signature = req.headers['x-fansly-signature'] as string; const rawBody = (req as any).rawBody; if (!signature || !rawBody) return res.status(400).send('Missing signature'); // 1. Calculate expected HMAC-SHA256 hash const computedHash = createHmac('sha256', WEBHOOK_SECRET) .update(rawBody) .digest('hex'); // 2. Constant-time signature validation const signatureBuffer = Buffer.from(signature, 'utf8'); const computedBuffer = Buffer.from(computedHash, 'utf8'); if (signatureBuffer.length !== computedBuffer.length || !timingSafeEqual(signatureBuffer, computedBuffer)) { return res.status(401).send('Signature verification failed'); } // 3. Prevent replay attacks via idempotency keys const event = req.body; const idempotencyKey = event.idempotencyKey || event.id; if (processedEvents.has(idempotencyKey)) { return res.status(200).json({ status: 'duplicate_ignored' }); } processedEvents.add(idempotencyKey); // Process event and acknowledge quickly return res.status(200).json({ received: true }); }); ``` ## Conclusion Deploying high-performance creator management tools requires robust API documentation and secure practices. By properly scoping API keys, adhering to the millidollar standard for financial data, and establishing a secure real-time API connection using HMAC webhook verification, you can bypass the unreliability of scraping scripts. Leveraging the extensive library of API endpoints provided by the Fansly platform ensures that your agency infrastructure scales efficiently, securely, and profitably. --- # Fansly vs OnlyFans for Creators and Agencies (2026 Comparison) Canonical: https://www.fansly-api.com/blog/fansly-vs-onlyfans > Honest 2026 comparison of Fansly and OnlyFans: fees, subscription tiers, audience size, content rules, payouts, and what agencies running 10+ creators need. **TL;DR** - Both platforms charge a 20% commission. The real differences are tier structure (Fansly multi-tier vs OnlyFans single), audience size (OnlyFans ~370M users vs Fansly ~130M), content rules (Fansly more permissive), and discovery (Fansly has a native For You Page, OnlyFans does not). - Solo creators usually do best on OnlyFans because of audience volume. Fansly wins for creators whose content is restricted on OnlyFans, who value multi-tier pricing, or who want platform-native discovery. - Agencies managing 5+ creators almost always run both platforms in parallel. The operational challenge is not picking one — it is scaling DM scheduling, revenue exports, and fan segmentation across both. Should you launch on Fansly or OnlyFans? The honest answer depends on who is asking. For a solo creator picking a first platform, the right choice is rarely one-size-fits-all — content niche, existing audience, and content rules all push the decision in different directions. For an agency managing 10+ creators, the right choice is usually **both**, and the real challenge is operational scaling across two platforms. This guide covers what actually differs between Fansly and OnlyFans in 2026 — platform fees, subscription structure, audience size, content rules, payouts, discovery — and what each difference means in practice for creators and agencies. ## Fansly vs OnlyFans — quick decision summary | Factor | Fansly | OnlyFans | |---|---|---| | Founded | 2020 | 2016 | | Headquarters | Baltimore, US | London, UK | | Platform fee | 20% | 20% | | Subscription model | Multiple tiers per creator | Single tier per creator (historically) | | Registered users (2024-25) | ~130M | 300M-370M | | Registered creators | Not public | 4M+ (2024) | | Content rules | More permissive (fetish, niche, cosplay) | Stricter (some kinks, cannabis, extreme content restricted) | | Discovery / algorithm | Built-in For You Page, search, filters | No native discovery — 100% external traffic | | Payout processing | 1-2 business days | 3-5 business days | | Pending period | 7 days | 7-21 days | | Payout methods | Bank, Paxum, some crypto | Bank, direct deposit | The summary line: **OnlyFans wins on audience size and creator economy maturity. Fansly wins on tier flexibility, content freedom, and platform-native discovery.** ## Revenue split — the 20% question Both platforms take a 20% commission on subscriptions, tips, and pay-per-view content. Creators keep 80% in both cases. There is no fee advantage to either platform. What this means in practice: a fan paying $10/month for a subscription yields $8 to the creator on both platforms (before tax, before any payment-processor or chargeback adjustments). OnlyFans has paid out more than $25 billion to creators since 2016 — proof the model works at scale. Fansly has not published cumulative payout figures. If anyone tells you Fansly takes less than OnlyFans, they are repeating outdated information. The fee structure is identical. ## Subscription model and tiers The structural difference matters more than most creators realize. **Fansly** lets each creator set **multiple paid subscription tiers** at different prices. A creator can offer a $5/month tier with basic content, a $15/month tier with weekly PPV included, and a $50/month tier with custom requests and direct chat. Each fan picks the price-value level they want. **OnlyFans** has historically supported a **single subscription price per creator page**. To run tiered pricing, an OnlyFans creator typically operates multiple separate accounts (a free account + a paid account, or a low-priced account + a high-priced account) — operationally more complex. For creators with monetizable depth (custom content, premium tiers, super-fan offers), Fansly's multi-tier model is structurally easier to monetize. For creators with broad mass-market content, OnlyFans's single-tier simplicity removes friction at the buying decision. ## Audience size and discoverability This is where OnlyFans's eight-year head start shows. **OnlyFans**: 370 million registered users, 4+ million creators, $25 billion paid out cumulatively (2024-2025 data). The platform reports more than $200 million paid to creators per month. The user base is global, with deep penetration in English-speaking markets and translated apps for many regions. **Fansly**: roughly 130 million registered users (2025 estimate from comparison sources). Creator count is not publicly disclosed. The platform is growing but operates at roughly one-third the scale of OnlyFans. The discoverability difference is even bigger. **OnlyFans has no native discovery** — no recommendation algorithm, no feed, no "creators you might like" surface. Creators drive 100% of their own traffic from external channels (Twitter/X, Reddit, Instagram, TikTok). This rewards creators who already have a social audience and punishes those who do not. **Fansly has a built-in For You Page** that surfaces creators algorithmically based on fan engagement. Hashtag search and creator browsing work natively. A creator without strong external traffic can be found organically on Fansly in a way that is structurally impossible on OnlyFans. For creators with weak existing audiences, Fansly's discovery is a real advantage. For creators with strong external traffic engines, OnlyFans's bigger pond pays off. ## Content rules — what each platform allows This is the deciding factor for many creators. **Fansly is consistently more permissive.** Fetish content, certain kinks, cosplay, NSFW art, cannabis-related content, and trans / non-binary creator content all face fewer restrictions on Fansly. The platform was deliberately built to welcome content categories where OnlyFans enforcement has been inconsistent. **OnlyFans is stricter on edge cases.** While explicit content is allowed (the August 2021 ban was reversed within a week), the platform periodically tightens enforcement around specific content types. Some kinks, cannabis content, and extreme categories have been flagged or removed. Enforcement varies and creators report mixed experiences. **Both platforms ban illegal content** (CSAM, non-consensual content, anything depicting minors) and require ID-based age verification before payouts. If your content niche has been demonetized or removed on OnlyFans in the past, Fansly is structurally safer for you. ## Payouts — speed, methods, holds As of 2025, the practical differences: **Fansly** - Processing: 1-2 business days after request - Pending period: 7 days from fan transaction - Methods: bank transfer, Paxum, some crypto support - Tax: 1099 contractor framing for US creators **OnlyFans** - Processing: 3-5 business days after request - Pending period: 7-21 days depending on transaction type - Methods: bank transfer, direct deposit - Tax: W2-style reporting in some jurisdictions For creators living paycheck-to-paycheck or paying chatters monthly, Fansly's faster payouts and shorter pending period materially affect cash flow. Always verify the current payout schedule directly in each platform's settings — rules change. ## Built-in creator tooling Both platforms offer basic creator dashboards: revenue summaries, fan lists, message threading, post scheduling. Neither platform is built for serious agency-scale operations. Once a creator earns $20K+/month or an agency manages 5+ accounts, the native tools become bottlenecks: - No bulk DM scheduling across creators - No unified revenue reporting across accounts - No fan-segmentation by spend tier or activity - No team management for chatters with different permissions - No automated win-back on churned subscribers This is why professional agencies route operations through third-party API platforms. ## For agencies — the operational reality The "Fansly vs OnlyFans" question is mostly the wrong frame for an agency at scale. Most professional creator agencies run **both platforms in parallel**: - A different roster on each platform based on creator content fit - Diversification protects against platform-specific policy changes or account suspensions - A creator who maxes out one platform can expand to the other for additional revenue The real challenge is not the platform choice — it is the operational complexity of running 10, 20, or 50 creator accounts across two platforms simultaneously. What breaks at scale on native tooling alone: | Pain point | Hours/week lost (rough) | Native fix? | |---|---|---| | DM scheduling across 20 creators | 30-40 | None | | Monthly revenue reconciliation across both platforms | 4-8 | None | | Fan segmentation by spend/activity | 5-10 | None | | Welcome / re-engagement / winback campaigns | 10-15 | None | | Multi-creator dashboard for the whole roster | 0 (does not exist natively) | None | The collective time loss across 20 creators is typically 30-50 hours per week of manual operations work — full-time-equivalent of one team member just doing copy-paste DM work. This is the gap third-party APIs fill. The [Fansly API](/pricing) (and equivalent OF platforms for OnlyFans creators) exposes the operational primitives — mass messaging, revenue exports, fan segmentation, webhooks — that native dashboards lack. If you are running 5+ creators on either platform, you will eventually face the build-vs-buy decision on agency operations tooling. The math is straightforward: 30-40 hours of saved manual work per week pays for the tooling at almost any plan tier. ## Which platform should you choose? For a **solo creator**: - **Choose OnlyFans** if your content is mass-market, you have strong external traffic (Twitter/X, Reddit), and your niche is comfortably within OnlyFans's content rules - **Choose Fansly** if your content is fetish/niche/cosplay, you want multi-tier pricing flexibility, you lack a strong social audience and need platform-native discovery, or your content has been restricted on OnlyFans - **Choose both** if you have the bandwidth — diversifies revenue against platform-specific risk For an **agency**: - Operate on both platforms unless there is a specific reason not to - Route each creator to the platform where their content + audience fit best - Invest in API tooling once you cross 5+ creators on either platform — the operational scaling problem is the actual ceiling on revenue growth, not platform choice ## Fansly vs OnlyFans — frequently asked questions **Which platform pays creators more — Fansly or OnlyFans?** Both platforms take 20% commission, so creators keep 80% on each. The difference is volume: OnlyFans has roughly 3x more users (300M-370M vs Fansly's ~130M), so the same creator typically earns more on OnlyFans simply because there are more potential subscribers to find them. **Can creators be on both Fansly and OnlyFans?** Yes. Many serious creators and most professional agencies operate on both platforms in parallel for revenue diversification and risk reduction. Posting cross-platform is allowed; just keep content unique enough to avoid fan refund requests on either side. **What content does Fansly allow that OnlyFans does not?** Fansly has consistently more permissive content rules — fetish content, certain kinks, cosplay, cannabis-related content, and trans/non-binary creator content all face fewer restrictions. OnlyFans periodically tightens enforcement on these categories. Both platforms still ban illegal content and require ID-based age verification. **Is Fansly safer than OnlyFans for creator accounts?** Both platforms enforce ID + face verification for new creator accounts. Account safety depends more on creator behavior (avoiding ToS-violating content, not sharing accounts) than on the platform itself. Both have suspended accounts; both have reinstated some on appeal. **Does Fansly pay out faster than OnlyFans?** As of 2025, Fansly typically processes payouts in 1-2 business days vs OnlyFans's 3-5 business days, and Fansly's pending period is 7 days vs OnlyFans's 7-21 days. Methods differ too: Fansly supports bank transfer, Paxum, and some crypto; OnlyFans uses bank transfer and direct deposit. Verify current schedules in each platform's payout settings. **Why does OnlyFans have a much bigger audience than Fansly?** OnlyFans launched in 2016, four years before Fansly (2020), and built an enormous head start during the 2020-2021 creator-economy surge. The platform reports 370 million registered users and over 4 million creators (2024 data), and has paid out more than $25 billion to creators since launch. **Can agencies manage creators on both Fansly and OnlyFans at scale?** Yes — multi-platform is the norm for professional agencies. The operational challenge is not the platform choice but unifying DM scheduling, fan segmentation, revenue exports, and tracking link attribution across both platforms. Most agencies use third-party API tooling for one or both platforms once they exceed 5-10 connected creators. **Which platform is better for a new creator starting out?** For most new creators with limited audiences, OnlyFans's larger user base and external-marketing model converts better when the creator drives their own traffic from social media. Fansly works better for creators whose content niche is restricted on OnlyFans, who want to test multi-tier pricing, or who lack a strong social audience and need the platform's native For You Page to surface them. ## Conclusion Fansly and OnlyFans answer different questions for creators and agencies. For solo creators, the choice is real — your content niche, your audience, and your content rules push toward one or the other. For most creators with broad content and existing social traffic, OnlyFans's audience wins. For creators with niche content or who lean on platform-native discovery, Fansly wins. For agencies, the choice is usually false. Multi-platform is the norm. The real problem is **operational scaling** — how to run 20 creators across two platforms without burning 50 hours a week on manual DM scheduling, revenue exports, and fan segmentation. If Fansly is part of your stack and you are scaling beyond 5 creators, [Fansly API](/register) handles the operational side — exports, automation, attribution, webhooks. Free tier to test, paid plans from $69/month. Questions? Reach out via [email](mailto:hello@fansly-api.com) or [Telegram](https://t.me/onlyfansapi_updates). ## Key definitions - **Subscription tier**: A pricing level a creator offers. Fansly supports multiple paid tiers per creator; OnlyFans has historically used a single tier per page. - **For You Page (FYP)**: A platform-native feed that surfaces creators to fans algorithmically, similar to TikTok or Instagram Explore. Fansly has one; OnlyFans does not. - **Pending period**: Time between a fan transaction and when funds become withdrawable by the creator. Used by platforms for chargeback protection. ## Key data points - API requests & webhooks processed: 150M+ (/about-us#statistics) - Companies using Fansly API: 500+ (/about-us#statistics) - Developer/operations hours saved: 220K+ (/about-us#statistics) ## Frequently asked questions ### Which platform pays creators more — Fansly or OnlyFans? Both platforms take 20% commission, so creators keep 80% on each. The difference is volume: OnlyFans has roughly 3x more users (300M-370M vs Fansly's ~130M), so the same creator typically earns more on OnlyFans simply because there are more potential subscribers to find them. ### Can creators be on both Fansly and OnlyFans? Yes. Many serious creators and most professional agencies operate on both platforms in parallel for revenue diversification and risk reduction. Posting cross-platform is allowed; just keep content unique enough to avoid fan refund requests on either side. ### What content does Fansly allow that OnlyFans does not? Fansly has consistently more permissive content rules — fetish content, certain kinks, cosplay, cannabis-related content, and trans/non-binary creator content all face fewer restrictions. OnlyFans periodically tightens enforcement on these categories. Both platforms still ban illegal content and require ID-based age verification. ### Is Fansly safer than OnlyFans for creator accounts? Both platforms enforce ID + face verification for new creator accounts. Account safety depends more on creator behavior (avoiding ToS-violating content, not sharing accounts) than on the platform itself. Both have suspended accounts; both have reinstated some on appeal. ### Does Fansly pay out faster than OnlyFans? As of 2025, Fansly typically processes payouts in 1-2 business days vs OnlyFans's 3-5 business days, and Fansly's pending period is 7 days vs OnlyFans's 7-21 days. Methods differ too: Fansly supports bank transfer, Paxum, and some crypto; OnlyFans uses bank transfer and direct deposit. Verify current schedules in each platform's payout settings. ### Why does OnlyFans have a much bigger audience than Fansly? OnlyFans launched in 2016, four years before Fansly (2020), and built an enormous head start during the 2020-2021 creator-economy surge. The platform reports 370 million registered users and over 4 million creators (2024 data), and has paid out more than $25 billion to creators since launch. ### Can agencies manage creators on both Fansly and OnlyFans at scale? Yes — multi-platform is the norm for professional agencies. The operational challenge is not the platform choice but unifying DM scheduling, fan segmentation, revenue exports, and tracking link attribution across both platforms. Most agencies use third-party API tooling for one or both platforms once they exceed 5-10 connected creators. ### Which platform is better for a new creator starting out? For most new creators with limited audiences, OnlyFans's larger user base and external-marketing model converts better when the creator drives their own traffic from social media. Fansly works better for creators whose content niche is restricted on OnlyFans, who want to test multi-tier pricing, or who lack a strong social audience and need the platform's native For You Page to surface them. --- # Connect Fansly to n8n: Native Integration Setup Canonical: https://www.fansly-api.com/blog/fansly-n8n-integration > Use Fansly with n8n, the only Fansly API with a native n8n node. Add the Fansly node to a workflow, paste your API key, and run one playbook for every creator. **TL;DR** - Native Fansly n8n node — no install, no permissions, no community-node battles. Setup takes under 5 minutes. - Replace 40 hours/week of manual DM scheduling, revenue exports, and fan tracking with workflows that run across every creator on your roster. - One technical setup, then non-technical chatters and ops edit workflows in the visual editor — no engineering tickets. Running multiple creators on Fansly without automation looks the same in every agency: spreadsheets per creator, 8-hour DM scheduling sessions, end-of-month revenue reconciliation panic, and "where did that $3,000 come from" Slack threads. **n8n + the native Fansly API node** lets you build one workflow and run it across every creator on your roster — no custom code, no engineering team, no fragile scripts. This guide covers the setup, the workflow patterns that pay back the fastest, and the tradeoffs to think about before scaling across a 10+ creator roster. ## What "native Fansly n8n integration" actually means Most third-party integrations on n8n live as **community nodes** — packages you have to install separately, often blocked by admin permissions or self-hosted environments. The Fansly node is different: it ships inside n8n by default. Open any workflow, search "Fansly" in the node panel, and the integration is right there. For an agency, this matters in three concrete ways: 1. **No engineer required for ongoing edits** — once setup is done, your chatters and ops team edit workflows in the visual editor 2. **Same setup on every n8n instance** — n8n Cloud, self-hosted, or a client's environment all behave identically 3. **Updates ship for free** — when n8n updates, the Fansly node updates with it. Your workflows do not break overnight. ## How to set up Fansly in n8n (under 5 minutes) 1. **Open n8n** — either n8n Cloud (free tier works) or your self-hosted instance 2. **Add a node** — click the + icon in any workflow, search `Fansly` in the search bar 3. **Pick an operation** — Accounts, Fans, Chats, Messages, Posts, Media, Earnings, Stories, Tracking Links, Webhooks 4. **Add your API key** — paste the key from your Fansly API dashboard once. It's stored as a credential and reused across every Fansly node in every workflow. 5. **Configure** — pick the connected creator account, set filters, define the payload 6. **Test** — click "Test step", verify the response, then chain into the rest of the workflow That's the entire setup. Most agencies have their first working workflow in under five minutes after the dashboard is open. ## What you can build (with the real outcomes attached) These are the patterns that pay back the fastest for agencies running multiple creators: ### Whale alerts → catch big tips in minutes, not next morning Trigger on the `tip.received` webhook, filter for amounts above a threshold (we see most agencies set $100 or $500), and post to a Slack channel or a chatter's Telegram in real time. **Why it matters:** the window for re-engaging a whale fan is **measured in minutes**, not hours. Manual end-of-day reviews catch them after the moment is gone. Real-time alerts turn a single $500 tip into a $2,000 subscription extension on the same day. ### Mass DM scheduling → 10,000 DMs in 30 minutes, not 8 hours Cron trigger fires on your schedule, pulls a fan segment via List Fans, runs Send Message in a loop with personalized templates and built-in rate-limit handling. **Why it matters:** an agency manually scheduling DMs across 20 creators burns roughly 40 hours per week. The same job runs in 30 minutes inside n8n — and you can A/B test templates, segment by spend tier, and exclude recently-messaged fans automatically. ### Revenue export → end the "where did this come from" Slack threads Daily cron pulls tracking link revenue + earnings + fan LTV across every creator, formats rows, appends to a Google Sheet your finance team owns. Connect Looker Studio or your BI tool for live dashboards. **Why it matters:** month-end reconciliation across 20 creators eats an afternoon every cycle. With this workflow, your numbers are clean and attributed by the time the month closes — and finance stops pinging you on Slack. ### Churn re-engagement → automatic winback on expired subs Trigger on `subscription.expired`, wait 7 days, send a personalized DM with a discount code generated from the Promotions endpoint. Measure conversion with a tracking link. **Why it matters:** roughly 15-25% of expired subs come back with a single well-timed winback message. Across 5,000+ fans per agency, this is real recurring revenue you currently lose to "we'll get to it eventually." ### AI chatbot → 24/7 personalized chat without hiring more chatters Trigger on `message.received`, pass message + recent context to an OpenAI / Claude / OpenRouter node, send response via Send Message. Add a fan-notes lookup so the bot knows fan history. **Why it matters:** chatters cost $3,000-$8,000/month per creator. An AI assistant handles tier-1 messaging for $50-$200/month in API costs. Your chatters move up to high-value conversations and PPV pitching. ### Cross-platform sync → unified CRM without writing code Trigger on Fansly events, push fan data to HubSpot, Notion, Airtable, or Pipedrive via their native n8n nodes. Build a real CRM your team uses instead of spreadsheets. **Why it matters:** you stop losing fan context every time a chatter goes on vacation or changes accounts. The fan history lives in your CRM, not in scattered DM threads. ## Tips before you scale across your roster - **Start with one creator, prove the workflow, then duplicate.** Most agencies break things by deploying everywhere at once. Validate one workflow on one account for a week before rolling out. - **Use webhooks, not polling.** A polling cron checking for new messages every minute costs more credits than HMAC-signed webhooks and adds latency. Webhooks scale linearly with events; polling scales with time. - **Add error handling early.** Wrap critical operations in n8n's Error Trigger workflow to ping your ops Slack when something fails. Better to find out at 9am Monday than during a $5k campaign. - **Batch list operations.** Pull 100 fans per call with pagination instead of one-at-a-time loops. Cuts credit burn by 10-50x on segmentation workflows. - **Monitor credit burn.** Daily Credit History in the Fansly dashboard shows trends. Set a Slack alert when a workflow consumes more than expected — a stuck loop can burn a day's credits in an hour. ## Pricing for n8n workflows Each API call inside an n8n workflow consumes Fansly API credits the same as a direct API call. Webhook deliveries cost 1 credit per 100 events. - **Basic — $69/month:** 20,000 credits, 1 account, native n8n included - **Pro — $299/month:** 100,000 credits (doubled from 75k), 5 accounts, full webhook access - **Enterprise — 100+ accounts:** dynamic pricing as low as $11.60 per account, custom credits, dedicated support For agencies running 20+ creators, dynamic pricing brings the per-creator cost below $30/mo — usually less than the manual hours saved in a single day. See the [full pricing page](/pricing) for credit allowances and overage rates. ## Frequently asked Fansly n8n integration questions **Do I need a developer to use the Fansly n8n integration?** One technical person sets up the first workflow — usually a morning's work. After that, your chatters, ops, and account managers edit existing workflows in n8n's visual editor with no code. Most agencies run dozens of workflows long after the developer moves on. **How much agency time does the Fansly n8n integration save?** Agencies running 10-20 creators typically cut 30-40 hours per week of manual work: DM scheduling, revenue exports, fan segmentation, churn re-engagement. That time goes back to creators, paid traffic, and growth. **Do I need to install the Fansly n8n node manually?** No. The Fansly node is native to every n8n instance. Open any workflow, search "Fansly" in the node panel, and it appears. No npm install, no JSON import, no community node permissions. **Can I trigger n8n workflows from Fansly events in real time?** Yes. Every Fansly event — new tip, new message, new subscriber, renewal, expired sub — fires an HMAC-signed webhook. Drop the n8n Webhook node URL into the Fansly dashboard and your workflow runs the moment the event happens. **Will n8n workflows count against my Fansly API credits?** Yes — same as direct API calls. Webhook triggers cost 1 credit per 100 events, which is cheaper than polling. The Daily Credit History dashboard shows usage so finance can budget accurately as you scale your roster. ## What changed in the December 2025 release This guide reflects the December 2025 Fansly API release which introduced: - **Native n8n integration** — searchable in every n8n instance, no install required - **Pro plan credits doubled** — 75,000 → 100,000 per month, same price - **Full Story API** — 8 Stories endpoints + 7 Story Highlights endpoints - **Public profile sorting & filters** (Pro/Enterprise) — sort by likes, subscribers, subscribe price; filter by gender - **`lastReplyAt` column** on fan endpoints — track who replied and when, perfect for chatter handoff - **New webhook properties + events** — `previous_reply_at` on fan webhooks, new `subscriptions.renewed` event - **Daily Credit History dashboard** — backfilled 10 days, full historical visibility for finance - **Dashboard chart upgrades** — smart x-axis labels, formatted y-axis numbers, custom date picker - **Search on List Fans + List Following** — `query` parameter for fast filtering - **Vault speed improvements** — significantly faster media access - **Smarter docs chatbot** + improved documentation search Follow [@onlyfansapi_updates on Telegram](https://t.me/onlyfansapi_updates) for the latest updates. --- Ready to scale your roster? [Sign up free](/register) — first 10 credits included, no credit card required. Questions? Reach out via [email](mailto:hello@fansly-api.com) or [Telegram](https://t.me/onlyfansapi_updates). ## Key definitions - **n8n**: An open-source workflow automation tool with 500+ pre-built integrations. Self-hostable free, or managed on n8n Cloud. - **Native node**: A Fansly integration that ships inside n8n by default — searchable in the workflow editor without any installation step. - **Workflow**: A visual chain of steps in n8n that runs on a schedule, webhook, or manual trigger. Edit in the browser, no code required. ## Key data points - API requests & webhooks processed: 150M+ (/about-us#statistics) - Companies using Fansly API: 500+ (/about-us#statistics) - Developer/operations hours saved: 220K+ (/about-us#statistics) ## Frequently asked questions ### Do I need a developer to use the Fansly n8n integration? One technical person sets up the first workflow — usually a morning's work. After that, your chatters, ops, and account managers edit existing workflows in n8n's visual editor with no code. Most agencies run dozens of workflows long after the developer moves on. ### How much agency time does the Fansly n8n integration save? Agencies running 10-20 creators typically cut 30-40 hours per week of manual work: DM scheduling, revenue exports, fan segmentation, churn re-engagement. That time goes back to creators, paid traffic, and growth. ### Do I need to install the Fansly n8n node manually? No. The Fansly node is native to every n8n instance. Open any workflow, search 'Fansly' in the node panel, and it appears. No npm install, no JSON import, no community node permissions. ### Can I trigger n8n workflows from Fansly events in real time? Yes. Every Fansly event — new tip, new message, new subscriber, renewal, expired sub — fires an HMAC-signed webhook. Drop the n8n Webhook node URL into the Fansly dashboard and your workflow runs the moment the event happens. ### Will n8n workflows count against my Fansly API credits? Yes — same as direct API calls. Webhook triggers cost 1 credit per 100 events, which is cheaper than polling. The Daily Credit History dashboard shows usage so finance can budget accurately as you scale your roster. --- # Fansly API Integration Guide: Setup, Webhooks & Endpoints Canonical: https://www.fansly-api.com/blog/fansly-api-integration-guide > Integrate the Fansly API end-to-end. Step-by-step guide to setup, webhooks, credits, team management, and the endpoints you need for production Fansly tools. **TL;DR** - Webhooks cost 1 credit per 100 events and fire on every message, sale, renewal, subscription, tip, and chat event with HMAC-SHA256 signing. - 200+ live endpoints cover accounts, fans, chats, earnings, posts, media, stories, statistics, and tracking links. - Team management, full request logs, dashboard analytics, and a public status page give production-grade visibility from day one. If you're building a Fansly tool — CRM, automation, dashboard, or full agency platform — the Fansly API gives you authenticated access to 200+ live endpoints with real-time webhooks. This guide walks through everything you need to ship a production integration: account setup, webhook handling, credit budgeting, team access, and operational monitoring. ## What you need before integrating the Fansly API Three things are required for any Fansly API integration: 1. **A Fansly API account** — sign up free at [fansly-api.com/register](/register). The free tier includes 10 credits for testing any endpoint. 2. **An API key** — generated in the dashboard, scoped per-team-member, and rotated on demand. 3. **A Fansly creator account to connect** — required for authenticated calls that read or write creator-side data. Once you have these three, you're ready to make your first call. ## How Fansly webhooks work Webhooks are the production-grade alternative to polling. Every event in Fansly — new message, sale, renewal, subscription, tip, chat reaction — fires a webhook to the endpoint you register in the dashboard. Each webhook delivery includes: - **HMAC-SHA256 signature** in the `X-Fansly-Signature` header - **Event type** (`message.received`, `sale.completed`, `subscription.renewed`, `subscription.expired`, `tip.received`, `chat.reaction`, and more) - **Payload** with the full event data - **Idempotency key** to deduplicate retries Verify the signature before doing anything with the payload: ```javascript import { createHmac } from 'crypto' function verifyWebhook(body, signature, secret) { const expected = createHmac('sha256', secret) .update(body) .digest('hex') return signature === expected } ``` Then deduplicate on the idempotency key to make retries safe: ```javascript const seen = new Set() function handleWebhook(event) { if (seen.has(event.idempotencyKey)) return seen.add(event.idempotencyKey) // process the event } ``` Webhook pricing is 1 credit per 100 events delivered. Failed deliveries retry with exponential backoff and surface in the Webhook Logs page in the dashboard. ### Common webhook patterns - **Chatbot sync** — subscribe to `message.received`, run AI inference, send reply via the messaging endpoint - **Whale alerts** — subscribe to `tip.received`, fire a Slack/Telegram alert when amount exceeds a threshold - **CRM updates** — subscribe to `subscription.renewed` and `subscription.expired`, sync fan status to your CRM - **Revenue dashboards** — subscribe to `sale.completed`, write to your warehouse for real-time reporting ## Fansly API endpoint reference The Fansly API exposes 200+ endpoints across nine object categories. Key categories you'll integrate first: - **Accounts** — list connected accounts, refresh tokens, manage sessions - **Fans & Subscriptions** — list fans, get subscriber metrics, filter by status - **Chats & Messages** — send messages, manage chats, mute/unmute, pin/unpin, like/unlike, gallery, reply-to threads - **Earnings & Payouts** — daily payout scheduling, revenue breakdowns, chargeback tracking - **Posts & Media** — create posts, upload media to vault, manage media scraping with optionally never-expiring URLs - **Stories** — list, create, analyze Fansly Stories and Story Highlights - **User Lists** — create, update, add/remove users for segmented messaging - **Statistics** — overview metrics for fans, visitors, posts, with timeframe filtering - **Tracking Links** — generate trial and tracking URLs for campaigns Full endpoint reference becomes available after sign-up in the dashboard playground. ## Pricing and credits explained Credits are the unit of usage across the Fansly API. Each call, webhook, or media download consumes a known number of credits. - **Free tier:** 10 credits to test any endpoint - **Basic:** $69/month, 20,000 credits + 1,000 RPM, 1 account - **Pro:** $299/month, 50,000 credits + 10,000 per account + 5,000 RPM, 5 accounts - **Enterprise:** 100+ accounts with custom development, per-account pricing as low as $10 Webhook events are priced at 1 credit per 100 events. The Credits table on the Usage page breaks down consumption by feature — so you always know where your credits are going. See the full [pricing page](/pricing) for tier comparison. ## Frequently asked Fansly API integration questions **How long does Fansly API integration take?** Most teams have a working production integration in under an hour: account setup, API key generation, first authenticated call, and webhook subscription configuration. **What does Fansly webhook signing look like?** Every webhook is signed with HMAC-SHA256. Verify the signature header against your shared secret before processing the payload. Reject any request that fails verification. **How do I monitor Fansly API errors in production?** The Logs page in the dashboard shows every request, response, and error in real time. A public status page tracks uptime and incidents across all endpoints. **Can multiple developers work on the same Fansly API account?** Yes. Team management lets you invite developers with role-based access. No password sharing required — each team member has their own credentials and audit trail. **What happens if a Fansly webhook delivery fails?** Failed deliveries retry automatically with exponential backoff. Each retry includes the same idempotency key so your endpoint can safely deduplicate. The Webhook Logs page surfaces every attempt and final status. ## What changed in the October 2025 release This guide reflects the major October 2025 Fansly API release which introduced: - **100x cheaper webhooks** — pricing dropped from 1 credit per event to 1 credit per 100 events - **AI Chatbot in docs and dashboard** — context-aware support without leaving your workflow - **Daily payouts via the payment frequency endpoint** — automatic creator payouts - **Team invites & role-based access** — multi-developer Fansly API accounts - **Full Logs Overview** — every request, response, and error in the sidebar - **22+ new endpoints** — User Lists, Subscriber Metrics, Statistics Overview, Latest Fans, Chargebacks, Chat Media Gallery, Typing Indicator, message Pin/Mute/Like controls, Reply-To message support, and new List Chats filters Follow [@onlyfansapi_updates on Telegram](https://t.me/onlyfansapi_updates) for the latest updates. --- Ready to integrate? [Sign up free](/register) — first 10 credits included, no credit card required. Questions? Reach out via [email](mailto:hello@fansly-api.com) or [Telegram](https://t.me/onlyfansapi_updates). ## Key definitions - **Credits**: Usage units that measure your Fansly API consumption across endpoints, webhooks, and media downloads. - **Webhook**: A server callback that delivers Fansly event data to your endpoint the moment it happens — no polling required. - **Idempotency key**: A unique identifier on each webhook delivery that lets your endpoint safely deduplicate retried events. ## Key data points - API requests & webhooks processed: 150M+ (/about-us#statistics) - Companies using Fansly API: 500+ (/about-us#statistics) - Developer/operations hours saved: 220K+ (/about-us#statistics) ## Frequently asked questions ### How long does Fansly API integration take? Most teams have a working production integration in under an hour: account setup, API key generation, first authenticated call, and webhook subscription configuration. ### What does Fansly webhook signing look like? Every webhook is signed with HMAC-SHA256. Verify the signature header against your shared secret before processing the payload. Reject any request that fails verification. ### How do I monitor Fansly API errors in production? The Logs page in the dashboard shows every request, response, and error in real time. A public status page tracks uptime and incidents across all endpoints. ### Can multiple developers work on the same Fansly API account? Yes. Team management lets you invite developers with role-based access. No password sharing required — each team member has their own credentials and audit trail. ### What happens if a Fansly webhook delivery fails? Failed deliveries retry automatically with exponential backoff. Each retry includes the same idempotency key so your endpoint can safely deduplicate. The Webhook Logs page surfaces every attempt and final status. --- # Fansly Mass Messaging API: Send Bulk DMs at Scale Canonical: https://www.fansly-api.com/blog/fansly-mass-messaging > Send personalized Fansly mass messages to thousands of fans in minutes. API endpoints for queueing, scheduling, stats, and Saved-for-Later, plus no-code flows. **TL;DR** - The Fansly Mass Messaging API lets you send personalized DMs to thousands of fans in one call — with queueing, stats, scheduling, and Saved-for-Later support. - Agencies replace 30-40 weekly hours of manual chatter DM scheduling with one workflow that runs across every creator on the roster. - Native Zapier instant triggers and expanded Make.com modules let non-technical ops teams build messaging campaigns without code. The single biggest time sink in running a Fansly creator agency is **manual mass messaging** — chatters copying templates, scheduling DMs, segmenting fans, and clicking send across dozens of creator accounts. The Fansly Mass Messaging API turns that into one workflow per creator that runs in minutes, hits every fan with personalized content, and tracks who converted. This guide covers what the API does, how to set up a mass message campaign, the use cases that pay back fastest, and the credit budgeting agencies should think about before scaling. ## What Fansly mass messaging via API actually means A mass message on Fansly is a single DM sent to many fans at once. You can send it from the Fansly dashboard one creator at a time — or you can call the Mass Messaging API and ship the same message across every creator on your roster simultaneously, with personalized content per fan. The API exposes the full workflow: - **Send** — fire a mass message to a fan segment with one call - **Queue** — schedule messages for future delivery or A/B testing windows - **Stats** — pull open rates, click rates, conversion data per blast - **Saved for Later** — manage the draft queue programmatically (list, publish, delete, edit) - **Segmentation** — filter recipients by subscription tier, spend tier, last activity, or custom fan lists The same endpoints work whether you're sending to 100 fans on one creator or 100,000 fans across 20 creators. ## How to send a Fansly mass message via API The minimum viable mass message takes one API call: ``` POST /v1/mass-messages { "account_id": "creator-account-id", "text": "Hey {{name}}, new content just dropped 🔥", "recipients": "all_active_fans", "media_ids": ["media-id-1"], "price_cents": 999 } ``` The fields: - **`account_id`** — which connected creator the message is from - **`text`** — the message body, with `{{name}}` and other template variables - **`recipients`** — `all_active_fans`, `all_expired_fans`, `all_fans`, a custom list ID, or an explicit array of fan IDs - **`media_ids`** — optional, attach photos or videos to the message - **`price_cents`** — optional, makes the attached media pay-per-view (PPV) The Fansly API queues the deliveries, handles rate limits, and surfaces real-time progress via webhook so you know when the send is complete. For non-technical teams, the **same operation is available as a Zapier instant trigger or a Make.com module** — no code required after the initial setup. ## Mass messaging use cases that pay back fastest These are the campaign types agencies ship in their first week with the API: ### PPV blasts → $1,000-$20,000 per campaign per creator Schedule a PPV (pay-per-view) media blast on Fridays at 9pm in each creator's timezone. Personalize the opener per fan, attach the media, set a price. Watch revenue land in the tracking link dashboard. **Why it matters:** PPV is the highest-margin monetization on Fansly. Manual PPV scheduling per creator burns hours every week. One workflow per creator + one cron trigger sends the same campaign across the roster automatically. ### Welcome sequence → activate new subs in the first 48 hours Trigger on `subscription.created` webhook, wait 1 hour, send a personalized welcome DM. Wait 24 hours, send a follow-up with a low-priced PPV. Wait 48 hours, send a free preview to drive the next purchase. **Why it matters:** the first 48 hours of a Fansly subscription is when fans are most engaged. Agencies that automate welcome sequences see **3-5x higher first-week PPV conversion** vs. agencies that wait for chatters to manually reach out. ### Win-back on expired subs → recover 15-25% with one DM Trigger on `subscription.expired`, wait 7 days, send a personalized DM with a discount code from the Promotions endpoint and a tracking link to measure conversion. **Why it matters:** expired-sub winback is recurring revenue that most agencies leave on the table. A 20% recovery rate across 5,000 expired fans = 1,000 reactivated subs from one workflow. ### Birthday & holiday outreach → loyalty without manual effort Pull fan birthday data from the Fans endpoint, schedule a personalized birthday message with a special offer. Same pattern for Valentine's, Halloween, NSFW holidays, etc. **Why it matters:** fans who receive birthday outreach are **2-3x more likely to renew** at end of cycle. One workflow handles 5,000+ birthdays/year automatically. ### Saved for Later → schedule a week of content in 30 minutes Use the Saved for Later API to queue 7 days of mass messages in one sitting — Sunday night planning session for the whole week across every creator on your roster. **Why it matters:** instead of chatters logging in daily across 20 accounts to send messages, ops schedules a week of campaigns in 30 minutes on Sunday. Everything runs automatically. ### A/B test what actually converts Send variant A to 50% of a fan segment, variant B to the other 50%. Compare conversion via tracking links. Promote the winner across the full segment. **Why it matters:** "this template gets more replies" is anecdote until you measure. A/B testing turns chatter intuition into data — and reveals templates that work across creators vs templates that only work for one. ## Tips before you scale mass messaging across your roster - **Personalize beyond `{{name}}`.** Pull spend tier, days-since-last-purchase, or last message topic into the template. Generic blasts get reported as spam; personalized blasts get replies. - **Respect rate limits.** Each Fansly account has a messaging cap. The API handles pacing automatically, but plan large campaigns for off-peak windows to avoid queue backups. - **Always include a tracking link.** Without one, you cannot measure which campaign drove which revenue. Build attribution into every blast. - **Test segments before full sends.** Run a campaign to a 100-fan slice first. If the open/reply rate is low, kill it before burning credits on 10,000 fans. - **Watch for fan complaints.** Set up a webhook trigger on `message.received` to flag fans who reply with negative sentiment. The Fans endpoint's restrict/block actions let you handle them programmatically. ## Pricing for Fansly mass messaging Each mass message campaign consumes credits. The cost scales with recipient count, personalization depth, and attached media. Rough estimates per blast: - **1,000 fans, plain text** — ~30 credits - **10,000 fans, personalized** — ~150 credits - **10,000 fans + PPV media** — ~250 credits Plans and credit allowances: - **Basic — $69/month:** 20,000 credits, 1 account, Mass Messaging API included - **Pro — $299/month:** 100,000 credits, 5 accounts, full webhook access - **Enterprise — 100+ accounts:** dynamic pricing as low as $11.60 per account, custom credits A single PPV blast that generates $5,000 typically costs under $5 in API credits. The ROI math is straightforward. See the [full pricing page](/pricing) for credit allowances and overage rates. ## Frequently asked Fansly mass messaging questions **How many fans can I message in one Fansly mass message?** There is no hard cap on the fan count per mass message. The Fansly API queues and rate-limits deliveries safely so you can target 10,000+ fans in a single blast without triggering account flags. **Can I personalize each Fansly mass message?** Yes. Template variables let you insert fan name, last purchase amount, subscription tier, time since last message, and any custom data you store. Each fan receives a unique-feeling DM at scale. **Will the Fansly Mass Messaging API replace my chatters?** No — it removes the boring half. Mass messages handle the repetitive blasts (PPV drops, welcome sequences, win-backs) so chatters spend their time on high-intent 1:1 conversations and PPV upsells where their judgment actually matters. **How much does one Fansly mass message campaign cost in credits?** A mass message to 10,000 fans typically consumes 100-300 credits depending on personalization depth and media attachments. The Credits Calculator in the dashboard shows the exact cost before you hit send. **Can I A/B test Fansly mass messages?** Yes. Send variant A to one fan segment, variant B to another, compare conversion via tracking links or webhook responses, then scale the winner. Most agencies run 2-3 active tests per creator at any given time. ## What changed in the July 2025 release This guide reflects the July 2025 Fansly API release which introduced: - **Full Mass Messaging API** — send, queue, stats, Saved for Later, segmentation - **No-code integrations** — Zapier instant webhook triggers + expanded Make.com modules - **Notifications API** — list, search, mark as read programmatically - **Profile & Settings API** — 60+ profile and account settings via API - **Trial Link API** — create, view, delete, list trial subscribers - **Banking endpoints** — country/account details and financial data for accounting - **App-based 2FA support** — SMS, Authenticator apps, Face ID - **Webhook reliability upgrades** — 30M+ webhooks processed at this point with fewer rate-limit errors - **Rebuilt docs** with credit calculator - **Public status page** — real-time monitoring and outage alerts Follow [@onlyfansapi_updates on Telegram](https://t.me/onlyfansapi_updates) for the latest updates. --- Ready to scale your messaging? [Sign up free](/register) — first 10 credits included, no credit card required. Questions? Reach out via [email](mailto:hello@fansly-api.com) or [Telegram](https://t.me/onlyfansapi_updates). ## Key definitions - **Mass message**: A single Fansly DM sent to many fans at once, with optional personalization, segmentation, and scheduled delivery. - **Saved for Later**: Fansly's draft system for queueing mass messages before sending. The API exposes full CRUD for managing the queue programmatically. - **PPV blast**: A pay-per-view media message sent to a fan segment for one-time content monetization, typically driving $1,000-$20,000+ per campaign per creator. ## Key data points - API requests & webhooks processed: 150M+ (/about-us#statistics) - Companies using Fansly API: 500+ (/about-us#statistics) - Developer/operations hours saved: 220K+ (/about-us#statistics) ## Frequently asked questions ### How many fans can I message in one Fansly mass message? There is no hard cap on the fan count per mass message. The Fansly API queues and rate-limits deliveries safely so you can target 10,000+ fans in a single blast without triggering account flags. ### Can I personalize each Fansly mass message? Yes. Template variables let you insert fan name, last purchase amount, subscription tier, time since last message, and any custom data you store. Each fan receives a unique-feeling DM at scale. ### Will the Fansly Mass Messaging API replace my chatters? No — it removes the boring half. Mass messages handle the repetitive blasts (PPV drops, welcome sequences, win-backs) so chatters spend their time on high-intent 1:1 conversations and PPV upsells where their judgment actually matters. ### How much does one Fansly mass message campaign cost in credits? A mass message to 10,000 fans typically consumes 100-300 credits depending on personalization depth and media attachments. The Credits Calculator in the dashboard shows the exact cost before you hit send. ### Can I A/B test Fansly mass messages? Yes. Send variant A to one fan segment, variant B to another, compare conversion via tracking links or webhook responses, then scale the winner. Most agencies run 2-3 active tests per creator at any given time. --- # Fansly Webhooks Guide: Real-Time Events Without Polling Canonical: https://www.fansly-api.com/blog/fansly-webhooks-guide > Stop polling. Fansly webhooks push every fan event, sale, subscription, tip, and message to your server in real time, with HMAC signing and automatic retries. **TL;DR** - Fansly webhooks push events to your server in real time — every message, sale, subscription, tip, post like, and account status change. - Webhooks cost 1 credit per 100 events vs. polling that burns thousands of credits per day, making them 100-1000x cheaper at scale. - Set up takes 5 minutes: register an endpoint URL, copy the signing secret, verify HMAC-SHA256 signatures, and react to events as they happen. If your Fansly integration polls the API every minute to check for new messages, sales, or subscriptions, you are burning credits, adding latency, and missing events between polls. **Fansly webhooks flip the model**: every event in Fansly pushes to your server the moment it happens, with cryptographic signing, automatic retries, and a built-in idempotency contract for safe deduplication. This guide covers what events fire webhooks, how to set them up in under five minutes, how to handle them safely in production, and the agency use cases that justify the switch from polling. ## Why webhooks beat polling for Fansly Polling looks innocent: a cron job that hits the Fansly API every minute to ask "anything new?" In reality it has three expensive problems: 1. **Cost** — every poll consumes credits whether new events happened or not. A "every minute" poll across 20 creator accounts burns 28,800 calls/day. Webhooks for the same coverage cost a fraction. 2. **Latency** — between polls, events sit in the platform waiting. A whale tip happens at 9:00:15; your scraper notices at 9:01:00. The 45-second gap is where chatter follow-up windows close. 3. **Reliability** — polling races against rate limits. Webhook deliveries are queued by Fansly and retried until your server acknowledges them. Webhooks remove all three. One event = one HTTP delivery = one credit per 100 events. ## Fansly webhook event types Every meaningful event on a connected Fansly account fires a webhook. Common ones: | Event | Fires when | |---|---| | `message.received` | A fan sends a DM to a creator | | `message.sent` | The creator sends a DM (via API or platform) | | `sale.completed` | A fan completes a purchase (PPV, tip, subscription) | | `subscription.created` | A fan subscribes for the first time | | `subscription.renewed` | A fan's subscription auto-renews | | `subscription.expired` | A fan's subscription ends | | `tip.received` | A fan sends a tip | | `post.liked` | A fan likes a post | | `typing.started` | A fan starts typing in a chat | | `account.status_changed` | A connected account changes state | The full list is visible in the dashboard once you register an endpoint. New events ship regularly without breaking existing handlers. ## How to set up Fansly webhooks in 5 minutes 1. **Open the Fansly API dashboard** — go to the Webhooks section 2. **Add an endpoint** — paste your server URL (HTTPS only — Fansly does not deliver to HTTP) 3. **Pick events to subscribe to** — start with `message.received`, `sale.completed`, `subscription.renewed`, and `subscription.expired`. Expand later. 4. **Copy the signing secret** — store it in your environment as `FANSLY_WEBHOOK_SECRET` 5. **Test from the dashboard** — Fansly fires a test event so you can verify your server accepts and responds 200 6. **Go live** — toggle the endpoint to Active That's it. Your server starts receiving events the moment they happen. ## Verifying Fansly webhook signatures Every delivery includes an `X-Fansly-Signature` header. Verify it before processing any payload — otherwise an attacker could forge fake events. ```javascript import { createHmac } from 'crypto' function verifyWebhook(rawBody, signatureHeader, secret) { const expected = createHmac('sha256', secret) .update(rawBody) .digest('hex') return signatureHeader === expected } // In your handler: if (!verifyWebhook(req.rawBody, req.headers['x-fansly-signature'], process.env.FANSLY_WEBHOOK_SECRET)) { return res.status(401).send('invalid signature') } ``` Note the use of `rawBody` — you must hash the body **before** JSON parsing or middleware mutation. Most web frameworks have a raw-body mode you need to enable. ## Handling Fansly webhook retries safely Fansly retries any delivery that doesn't return a 2xx response, with exponential backoff. Your server may see the same event 2-5 times under flaky network conditions. Deduplicate using the idempotency key on every event: ```javascript const seen = new Set() // use Redis or a database for multi-instance setups async function handleWebhook(event) { if (seen.has(event.idempotencyKey)) { return // already processed, skip } seen.add(event.idempotencyKey) await processEvent(event) // safe to run business logic now } ``` For low-volume use cases (< 10k events/day per server), an in-memory Set works. For production with multiple workers, store keys in Redis with a 24-hour TTL. ## Agency use cases — what webhooks actually unlock Webhooks are not a developer convenience. They are the foundation of every revenue-driving automation an agency runs. ### Real-time whale alerts → catch tips in minutes Subscribe to `tip.received`, filter for amounts ≥ $100, push to a Slack channel or chatter Telegram. **Result:** chatters reach out while the fan is still in the conversation, not the morning after when the opportunity is gone. ### Welcome sequences → activate new subs in the first hour Subscribe to `subscription.created`. Wait 1 hour. Send personalized welcome DM via the messaging API. Wait 24 hours. Follow up with PPV. **Result:** 3-5x higher first-week revenue per new sub vs. waiting for manual chatter outreach. ### Churn winback → recover 15-25% of expired subs Subscribe to `subscription.expired`. Wait 7 days. Send a personalized DM with a discount code from the Promotions endpoint and a tracking link. **Result:** thousands of dollars in recovered MRR from a workflow that runs itself. ### Chatter routing → put the right person on the right fan Subscribe to `message.received`. Pull fan spend tier from the Fans endpoint. Route high-LTV fans to senior chatters, new fans to onboarders, dormant fans to retention specialists. **Result:** every fan gets the right level of attention without manual triage. ### Real-time revenue dashboards → finance stops asking Subscribe to `sale.completed` and `subscription.renewed`. Stream to BigQuery, Snowflake, or a Google Sheet via n8n / Zapier / Make.com. **Result:** finance team sees revenue land in their dashboard within seconds, not at month-end reconciliation. ### Compliance and content monitoring → catch problems before they escalate Subscribe to `message.received`. Run text through a moderation classifier (OpenAI Moderation API, Perspective API, or your own model). Flag and route problem messages to ops. **Result:** account safety risk dropped, manual review hours eliminated. ## Production tips for Fansly webhooks - **Respond 200 fast.** Acknowledge receipt, queue the event for async processing. Long synchronous handlers cause timeouts and trigger retries. - **Log every delivery.** Even with idempotency keys, keep a log of payload + response for audit and debugging. The dashboard has a Webhook Logs page that surfaces the Fansly-side view. - **Test failure modes.** Simulate slow database queries, third-party API outages, and storage failures. Your handler should never crash on a single bad event. - **Use HTTPS with valid certs.** Fansly does not deliver to HTTP endpoints or invalid TLS. Set up Let's Encrypt or AWS ACM if you don't already have it. - **Watch the dashboard.** The Webhook Logs page shows every delivery attempt, retry count, and final status. Set up an alert when failure rate exceeds 1% over a 5-minute window. ## Pricing for Fansly webhooks Webhook deliveries cost **1 credit per 100 events** — typically 100-1000x cheaper than polling-equivalent coverage. A creator account with high fan activity (5,000+ events/day across messages, likes, tips, subscriptions) costs ~50 credits/day in webhook deliveries. The same coverage with 1-minute polling would consume 1,440 calls/day at standard credit cost. Plans and credit allowances: - **Basic — $69/month:** 20,000 credits, 1 account, full webhook access - **Pro — $299/month:** 100,000 credits, 5 accounts, full webhook access - **Enterprise — 100+ accounts:** dynamic pricing as low as $11.60 per account, custom credits Webhooks are included on every paid plan — there is no premium tier required. See the [full pricing page](/pricing) for credit allowances and overage rates. ## Frequently asked Fansly webhook questions **What is the difference between polling and Fansly webhooks?** Polling means your server asks the Fansly API every minute (or every second) whether anything new happened. Webhooks mean Fansly tells your server the moment it happens. Webhooks are 100-1000x cheaper at scale, faster, and more reliable — there is no race condition where you miss events between polls. **Are Fansly webhooks reliable enough for production?** Yes. Every delivery includes an HMAC-SHA256 signature for verification, an idempotency key for safe retries, and automatic exponential-backoff retry on failure. We have processed 150M+ events with delivery guarantees that match enterprise standards. **Which Fansly events fire webhooks?** Messages received and sent, sales completed, subscriptions created, renewed, and expired, tips received, PPV purchased, post interactions, typing indicators, account status changes, and more. The full event list is available in the dashboard once you register an endpoint. **How do I handle Fansly webhook retries safely?** Every webhook delivery includes a unique idempotency key. Store the keys you have already processed (in Redis, a database, or even an in-memory set for low-volume cases) and skip any duplicate. Failed deliveries retry with exponential backoff until they succeed or time out. **Can I use Fansly webhooks without writing code?** Yes. n8n, Zapier, and Make.com all expose webhook trigger nodes. Paste the URL into the Fansly dashboard and your no-code workflow starts the moment the event fires — no server, no code, no infrastructure to maintain. ## What changed in the June 2025 release This guide reflects the June 2025 Fansly API release which introduced: - **Production webhooks** — real-time event delivery for messages, sales, subscriptions, tips, post interactions, typing indicators, and account state changes - **Make.com integration** — first no-code platform with full Fansly API coverage, prebuilt scenarios for transaction sync and link tracking - **Media management endpoints** — upload photos, videos, audio; organize vault media; create vault lists - **Post management** — schedule posts with labels, media, polls (regular and quizzes), fundraising targets, expiration dates - **Advanced chat messaging** — PPVs, media attachments, creator tags - **Text formatting** — bold, italic, color, and size in posts and messages Follow [@onlyfansapi_updates on Telegram](https://t.me/onlyfansapi_updates) for the latest updates. --- Ready to switch from polling? [Sign up free](/register) — first 10 credits included, no credit card required. Questions? Reach out via [email](mailto:hello@fansly-api.com) or [Telegram](https://t.me/onlyfansapi_updates). ## Key definitions - **Webhook**: An HTTP callback Fansly sends to your server the moment an event happens. The opposite of polling — you do not ask, the platform tells you. - **HMAC-SHA256 signature**: A cryptographic hash that proves a webhook came from Fansly and was not tampered with in transit. Verify before processing every delivery. - **Idempotency key**: A unique identifier on each webhook delivery. Use it to safely deduplicate retried events so the same payment is not credited twice. ## Key data points - API requests & webhooks processed: 150M+ (/about-us#statistics) - Companies using Fansly API: 500+ (/about-us#statistics) - Developer/operations hours saved: 220K+ (/about-us#statistics) ## Frequently asked questions ### What is the difference between polling and Fansly webhooks? Polling means your server asks the Fansly API every minute (or every second) whether anything new happened. Webhooks mean Fansly tells your server the moment it happens. Webhooks are 100-1000x cheaper at scale, faster, and more reliable — there is no race condition where you miss events between polls. ### Are Fansly webhooks reliable enough for production? Yes. Every delivery includes an HMAC-SHA256 signature for verification, an idempotency key for safe retries, and automatic exponential-backoff retry on failure. We have processed 150M+ events with delivery guarantees that match enterprise standards. ### Which Fansly events fire webhooks? Messages received and sent, sales completed, subscriptions created, renewed, and expired, tips received, PPV purchased, post interactions, typing indicators, account status changes, and more. The full event list is available in the dashboard once you register an endpoint. ### How do I handle Fansly webhook retries safely? Every webhook delivery includes a unique idempotency key. Store the keys you have already processed (in Redis, a database, or even an in-memory set for low-volume cases) and skip any duplicate. Failed deliveries retry with exponential backoff until they succeed or time out. ### Can I use Fansly webhooks without writing code? Yes. n8n, Zapier, and Make.com all expose webhook trigger nodes. Paste the URL into the Fansly dashboard and your no-code workflow starts the moment the event fires — no server, no code, no infrastructure to maintain. --- # Legal --- # Cookie Policy Canonical: https://www.fansly-api.com/cookies-policy > Cookies Policy for Fansly API — how Fans Holdings OÜ uses cookies and similar technologies, and how to control them. # Cookies Policy **Last updated: 16 June 2026** This Cookies Policy explains how **Fans Holdings OÜ** ("we", "us", "our") uses cookies and similar technologies on our websites and services (the "Service"). It should be read together with our [Privacy Policy](/privacy-policy). Registered address: Pille tn 9/3-53, Kesklinna district, Tallinn, Harju County, 10138, Estonia. Contact: hello@fansly-api.com. ## 1. What cookies are Cookies are small text files placed on your device when you visit a website. Similar technologies include local storage, pixels, and SDKs. They let a service function, remember preferences, and understand usage. ## 2. Categories we use - **Strictly necessary** — required to run the Service, sign you in, and keep it secure. These do not require consent. - **Functional** — remember your preferences and settings. - **Analytics** — help us understand how the Service is used so we can improve it. We do not use cookies for third-party advertising. Third parties that may set cookies through the Service include our payment processor (Stripe) and our analytics provider. ## 3. Your consent Strictly necessary cookies are always active. We set functional and analytics cookies **only with your consent**, which we collect through our cookie banner when you first visit. You can accept or reject non-essential cookies with equal ease, and you can change or withdraw your choice at any time through the banner or your cookie settings. ## 4. Managing cookies You can manage cookies through our cookie settings and through your browser, which lets you block or delete cookies. Blocking strictly necessary cookies may stop parts of the Service from working. ## 5. Changes and contact We may update this Cookies Policy and will post the revised version with a new "Last updated" date. Questions: hello@fansly-api.com. You may also complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon) or your local supervisory authority. --- # DMCA & 2257 Notice Canonical: https://www.fansly-api.com/dmca > DMCA copyright and 18 U.S.C. § 2257 record-keeping notice for Fansly API, including how to file a takedown request with Fans Holdings OÜ. # DMCA & 18 U.S.C. § 2257 NOTICE This Notice applies to the services operated by **Fans Holdings OÜ** ("we", "us", "our"), registered at **Pille tn 9/3-53, Kesklinna district, Tallinn, Harju County, 10138, Estonia**, VAT ID **EE102827084**. Contact: **hello@fansly-api.com**. --- ## **1. 18 U.S.C. § 2257 — record-keeping** We do not produce, create, host, store, or distribute any sexually explicit or adult content. Our service is a software tool that operates on accounts and platforms that our users connect and control. Accordingly, **18 U.S.C. § 2257 and § 2257A do not impose record-keeping obligations on us as a producer.** Any obligation to create and maintain age-verification and consent records for content lies with the users and the platforms that produce, upload, or host that content. By using our service, you confirm that every person depicted in, or who is a subject of, any account or content you connect is an adult (18+) who has consented, and that you comply with all applicable record-keeping and age-verification laws. --- ## **2. DMCA — copyright complaints** We respect intellectual-property rights and respond to valid notices under the U.S. Digital Millennium Copyright Act (DMCA) and applicable EU law. **Submitting a notice.** If you believe material accessible through our service infringes your copyright, send a written notice to **hello@fansly-api.com** including: (a) your contact details; (b) identification of the copyrighted work; (c) identification and location of the allegedly infringing material; (d) a statement that you have a good-faith belief the use is not authorised; (e) a statement that the information is accurate and, under penalty of perjury, that you are authorised to act for the rights holder; and (f) your physical or electronic signature. **Counter-notice.** If your material was removed and you believe this was in error, you may submit a counter-notice to the same address with equivalent information. **Repeat infringers.** We may suspend or terminate the accounts of users who repeatedly infringe. --- ## **3. Changes and contact** We may update this Notice and will post the revised version with a new "Last updated" date. Contact: **hello@fansly-api.com**. --- # Privacy Policy Canonical: https://www.fansly-api.com/privacy-policy > Privacy Policy for Fansly API: how Fans Holdings OÜ collects, uses, stores, and protects your personal data, and your rights under the GDPR. # PRIVACY POLICY ## **1. Who we are** This Privacy Policy explains how **Fans Holdings OÜ** ("we", "us", "our") handles personal data in connection with **Fansly API** (the "Service"), provided via fansly-api.com and the application at app.onlyfansapi.com. Read it together with our Terms of Service (including the data processing terms in Section 10) and our Cookies Policy. Registered address: **Pille tn 9/3-53, Kesklinna district, Tallinn, Harju County, 10138, Estonia**. VAT ID **EE102827084**. Privacy contact: **hello@fansly-api.com**. We will appoint a Data Protection Officer where required by law and publish their contact here. --- ## **2. Our two roles: controller and processor** **(a) As controller** — for personal data about **you, our customer** and your account users: registration, billing, support, and usage data. This Policy governs that data. **(b) As processor** — for personal data you bring into the Service from the platforms and tools you connect, including data about **subscribers, fans, and contacts**. For this data **you are the controller** and we process it only on your documented instructions, under the data processing terms in Section 10 of our Terms of Service. Requests from those individuals are directed to you as controller; we will assist you. --- ## **3. Personal data we process** **As controller (your account):** name, email, username, organisation, payment and transaction details, IP address, device and browser information, cookies and usage data, API logs, and your communications with us. **As processor (on your instructions):** data from the platforms and tools you connect, which may include subscriber/fan identifiers, message content, spend and purchase history, and preferences. **Special-category data.** Data about an identifiable person's use of an adult creator platform, and message content, **may reveal information about that person's sex life or sexual orientation — special-category data under Article 9 GDPR.** We do not seek such data for our own purposes; where it is processed, we do so only as your processor on your instructions, and **you are responsible** for ensuring a valid Article 9 condition (such as explicit consent) and lawful basis. --- ## **4. How we use your data and our legal bases (controller role)** - **To provide the Service** — account, access, API keys, support. *Basis: contract.* - **To take payment** — billing and fraud prevention. *Basis: contract; legal obligation.* - **To secure and improve the Service** — security, diagnostics, and product improvement using your account and usage data. *Basis: legitimate interests (assessment available on request).* - **To communicate with you** — service messages (contract/legitimate interests) and marketing where required (consent — withdraw anytime). - **To comply with law** — tax, accounting, lawful requests. *Basis: legal obligation.* We do **not** use personal data you process as a controller (subscriber/fan/contact data) to train any general or cross-customer AI model without your instructions or consent. --- ## **5. Sub-processors and AI providers** We use the following categories of sub-processor: **hosting and infrastructure** — Amazon Web Services (AWS) and Hetzner (the hosting region is selected in accordance with the customer's configuration and requirements); **payment processing** — Stripe; **AI / large-language-model providers** — Anthropic, Google, OpenAI, and xAI, under terms that do not permit them to use your data to train their models; and the **connected platforms and tools you choose** — Fansly. We maintain a current list and will give notice of changes so you can object, as set out in Section 10 of our Terms. --- ## **6. International transfers and data location** The location where data is hosted and stored is determined in accordance with the customer's configuration and requirements; where you require EU data residency, we host within the EU. Some sub-processors (certain AI providers and infrastructure) may be located outside the EEA, for example in the **United States**. Where we transfer personal data outside the EEA we rely on an adequacy decision, the EU **Standard Contractual Clauses** with supplementary measures, or another lawful mechanism. --- ## **7. Data sharing** We do not sell or rent personal data. We share it only with the sub-processors above, professional advisers, in a corporate transaction, and with authorities where legally required. We may create and use **aggregated, anonymised, or de-identified data** — which does not identify any individual — for any business purpose, including to operate, improve, develop, and commercialise our services. --- ## **8. Retention** Account data: for the life of your account, then deleted or anonymised within 90 days of closure unless the law requires longer. Transaction data: 7 years for tax and accounting. Technical/API logs: 12 months. Communications: 6 months unless needed for a legal claim. Processor data (subscriber/fan/contact data): only while needed to provide the Service, then deleted or returned on termination per Section 10 of our Terms. --- ## **9. Profiling and automated decisions** The Service may generate analytics involving **profiling** (for example scoring or segmenting fans or contacts). We do not make decisions producing legal or similarly significant effects about individuals based **solely** on automated processing without human involvement. Where you use these features, you remain the controller and are responsible for how decisions are made. --- ## **10. Your rights** Under GDPR you may request access, rectification, erasure, restriction, portability, objection to legitimate-interests processing, and withdrawal of consent, and may complain to a supervisory authority. For data we hold **as controller**, contact **hello@fansly-api.com**; we respond within **one month** (extendable by two months for complex requests, with notice). For data we hold **as processor**, contact the relevant customer (the controller); we will assist them. --- ## **11. Cookies** We use cookies and similar technologies. Strictly necessary cookies are always active; non-essential cookies are set only with your consent. Details are in our [Cookies Policy](/cookies-policy). --- ## **12. Security** We use appropriate technical and organisational measures, including encryption in transit and at rest, access controls, and regular review. No system is perfectly secure. **In the event of a personal-data breach, we will notify the relevant supervisory authority and affected individuals where required by law, and — as processor — notify affected customers without undue delay.** --- ## **13. Children** The Service is for adults (18+) only and is not directed to children. You must not use the Service to process the personal data of anyone under 18. --- ## **14. Changes** We may update this Policy and will communicate material changes by email or in-product before they take effect. --- ## **15. Contact and complaints** Fans Holdings OÜ, Pille tn 9/3-53, Kesklinna district, Tallinn, Harju County, 10138, Estonia. Email: **hello@fansly-api.com**. You may complain to the **Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon)** or your local supervisory authority. --- # Terms of Service Canonical: https://www.fansly-api.com/terms-of-service > Terms of Service for Fansly API: the agreement between you and Fans Holdings OÜ covering accounts, credits, acceptable use, and liability. # TERMS OF SERVICE ## **1. Who we are** Fansly API (the "**Service**") is operated by **Fans Holdings OÜ** ("**Company**", "**we**", "**us**", "**our**"), registered at **Pille tn 9/3-53, Kesklinna district, Tallinn, Harju County, 10138, Estonia**, VAT ID **EE102827084**. The Service is delivered through our backend at app.onlyfansapi.com regardless of which of our websites you registered through, and these Terms bind you however you access it. Fansly API is an independent service. **We are not affiliated with, endorsed by, sponsored by, or partnered with OnlyFans or Fansly, or their operating companies, subsidiaries, or affiliates — including Fenix International Limited and Fenix Internet LLC (OnlyFans) and Select Media LLC and CY Media LTD (Fansly).** We do not host, store, distribute, or produce adult content. By creating an account, generating an API key, connecting an account, or using the Service, you agree to these Terms. If you do not agree, do not use the Service. **These Terms place responsibility for third-party platform compliance on you (Section 5) and limit our liability (Section 12).** Nothing here removes any right you have under applicable mandatory law, including consumer-protection law. --- ## **2. The Service and your licence** Fansly API is an independent API and developer platform that provides programmatic access to data and actions on Fansly, which you connect using credentials and access you provide. We grant you a limited, non-exclusive, revocable right to use the Service during your subscription. You may resell, sublicense, or white-label the Service to your own clients. We are continuously developing the Service and may add, change, suspend, or discontinue features at any time; where a material change is within our control, we will use reasonable efforts to give notice. --- ## **3. AI-generated content** The Service uses artificial intelligence to generate drafts, suggestions, replies, and analyses ("**AI Output**") from the data and instructions you provide ("**Your Input**"). You acknowledge that: (a) AI Output may be inaccurate or unsuitable, and **you are solely responsible for reviewing it before it is sent, published, or relied upon**; (b) AI features are provided "as is" and we do not warrant the accuracy or fitness of any AI Output; (c) you retain your rights in Your Input and AI Output and grant us a limited licence to process them to provide the Service; and (d) we send only the data needed to fulfil a request to our AI providers, who are bound not to use it to train their own models. --- ## **4. Eligibility and your representations** By using the Service you represent and warrant that: you are at least **18 years old** and have authority to enter into these Terms (and, if acting for an organisation, authority to bind it); you are authorised to operate and connect every account you connect; **every person who is a subject of any account, content, or data you access is an adult (18+) who has consented**, and you meet all applicable age-verification and record-keeping obligations; you have a valid lawful basis for all personal data you process through the Service (Section 10); and you will not use the Service for any unlawful, fraudulent, deceptive, or infringing purpose. If you use the Service for business purposes, you confirm you are acting as a business and not as a consumer. --- ## **5. Your responsibilities and third-party platforms** The Service interacts with third-party platforms, including Fansly, each of which sets its own terms, and some restrict automation or third-party access. Because those rules are set by the platforms and can change at any time, **you are best placed to decide how to use the Service on your own accounts, and you remain responsible for ensuring your use complies with each platform's terms.** We can't monitor or guarantee that compliance for you, so any action a platform takes about your account — including suspension, restriction, ban, loss of access, or loss of earnings — **remains your responsibility rather than ours.** We will support you where we reasonably can, but we are not liable for a platform's decisions about your account, and a platform's changes to its terms or interfaces may interrupt or end functionality without liability to us. (This Section does not exclude liability that cannot be excluded under applicable law — see Section 12.) --- ## **6. Acceptable use and account security** You must not use the Service to: access or process content or data involving **minors**, or anything illegal where you or the data subjects are located; engage in fraud, harassment, or deception; process personal data without a valid lawful basis; infringe intellectual-property, privacy, or publicity rights; introduce malware or attack our systems; or circumvent usage limits, rate limits, or fees. **You are responsible for safeguarding your account credentials and API keys and for all activity that occurs under them.** We may suspend access immediately for breach of this Section. --- ## **7. Payments, subscriptions and refunds** **7.1 Plans and pricing.** The Service is offered on the plans, prices, and billing cycles shown at purchase, in the currency shown at checkout. We may introduce, change, or withdraw plans, prices, trials, and promotions at any time; the terms shown at purchase or renewal apply to that period. **7.2 Payment and authorisation.** Payments are processed by our payment processor, Stripe, using the methods offered at checkout. By subscribing, you authorise us and our processor to charge your payment method for the subscription and each renewal, including applicable taxes and fees. Your card issuer or payment provider may apply its own charges (for example, currency conversion). **7.3 Taxes.** Prices are exclusive of VAT and other applicable taxes, which we add where required. You are responsible for any taxes arising from your use of the Service, other than taxes on our income. **7.4 Auto-renewal.** Paid subscriptions renew automatically at the end of each billing cycle, for a further cycle of the same length, at the then-current price, until cancelled. **7.5 Cancellation.** You may cancel at any time from your account or by emailing **hello@fansly-api.com**. Cancellation stops the next renewal and takes effect at the end of your current billing cycle; you keep access until then. You are responsible for cancelling before a renewal if you do not want to be charged for the next cycle. **7.6 Refunds.** All fees are non-refundable. The only exception: if a critical failure prevents you from using the Service and we do not resolve it within 24 hours of your report to **hello@fansly-api.com**, we will refund the affected period. We may also reverse a duplicate charge or a charge resulting from proven unauthorised use of your payment method. We do not refund for non-usage, partial periods, or change of mind. Approved refunds are issued to your original payment method, normally within 10 business days. This does not affect rights that cannot be excluded by law. **7.7 Price changes.** We may change prices and plans at any time. A change to the price of an existing subscription applies from your next renewal, and you may cancel before it takes effect. **7.8 Failed payments.** If a payment fails, we may **suspend the Service immediately** and may terminate the subscription. **7.9 Chargebacks.** If you have a billing concern, contact us first at hello@fansly-api.com so we can resolve it. We reserve the right to contest improper chargebacks and to recover related fees and costs where permitted by law. --- ## **8. Right of withdrawal (consumers in the EU/EEA)** If you are a **consumer**, you have a right to withdraw within **14 days** of subscribing. By starting to use the Service during that period, you (a) expressly request that we begin during the period, and (b) acknowledge that you lose the right of withdrawal once the Service has been fully performed, and that if you withdraw while it is still being supplied you must pay a proportionate amount for what you have used. To withdraw, tell us clearly at hello@fansly-api.com before the period ends. Your statutory consumer rights are unaffected. --- ## **9. Service availability and no guarantee of results** We target **99.9% monthly availability** but do not warrant uninterrupted, timely, secure, or error-free operation. Maintenance, platform changes, and third-party outages may affect availability. The Service is a software tool; **we do not guarantee any particular results, earnings, growth, or outcomes** from your use of it. For business users, service credits we may offer are the sole remedy for downtime; consumers' statutory remedies are unaffected. --- ## **10. Data protection and processing terms** **10.1 Roles.** When the Service processes personal data from the accounts and tools you connect (data about your subscribers, fans, contacts, and staff), **you are the data controller** and **we act as your processor**, processing it only on your documented instructions (including these Terms). You are responsible for a valid lawful basis and any required consents or conditions, including for any special-category data (such as data that may reveal a person's sex life or sexual orientation). How we handle data for which we are the controller (your account and billing data) is in our Privacy Policy. **10.2 Processing details.** Subject matter: provision of the Service. Duration: the term of your subscription. Nature and purpose: hosting, analysing, generating, and transmitting data to operate the Service at your direction. Types of personal data: identifiers, contact details, message content, and transaction and engagement data. Categories of data subjects: your subscribers, fans, contacts, and personnel. **10.3 Our obligations as processor.** These terms satisfy Article 28 GDPR. We will: (a) process personal data only on your documented instructions, unless required by law (and then notify you unless prohibited); (b) ensure authorised persons are bound by confidentiality; (c) implement appropriate technical and organisational security measures under Article 32, including encryption in transit and at rest and access controls; (d) assist you, taking into account the nature of processing, with data-subject requests, security, breach notification, and DPIAs (Articles 32–36); (e) notify you without undue delay after becoming aware of a personal-data breach; (f) on termination, delete or return personal data at your choice, except where retention is required by law; and (g) make available information reasonably necessary to demonstrate compliance and allow audits on reasonable notice, subject to confidentiality and security conditions. **10.4 Sub-processors.** You authorise us to engage sub-processors to provide the Service, including those listed in our Privacy Policy (hosting, payment, and AI providers). We will give notice of any intended new or replacement sub-processor and you may object on reasonable data-protection grounds; we remain responsible for our sub-processors' performance. **10.5 International transfers.** Where we transfer personal data outside the EEA, we rely on the EU Standard Contractual Clauses or another lawful mechanism, with supplementary measures where appropriate. The location where data is hosted is determined in accordance with the customer's configuration and requirements. --- ## **11. Intellectual property, feedback and takedowns** The Service — our software, API design, documentation, and branding — is owned by us or our licensors. You may not use our trademarks or branding without written permission. You retain ownership of your data and content and grant us a licence to host, process, and transmit it to provide the Service. If you give us feedback or suggestions, you grant us a perpetual, royalty-free licence to use them without obligation to you. We do not host third-party platform content; we respond to valid copyright complaints under our DMCA & 2257 Notice. --- ## **12. Limitation of liability** Nothing here limits liability for: death or personal injury caused by our negligence; fraud; intent or gross negligence; or any liability that cannot be excluded under applicable law, including mandatory consumer rights. Subject to that, and **to the maximum extent permitted by law**: the Service is provided **"as is"** and **"as available"**; **you are solely responsible for your use of it and for all actions taken through it**; we are not liable for indirect, incidental, special, or consequential damages, or for loss of profits, revenue, data, goodwill, or business; we are not liable for any suspension, restriction, or ban imposed on you by a third-party platform, or for any third-party content or conduct; and our total aggregate liability in any 12-month period will not exceed the amounts you paid us for the Service in the 12 months before the event giving rise to the claim. --- ## **13. Indemnification (business users)** If you use the Service in the course of a business, you will indemnify and hold harmless Fans Holdings OÜ and its officers, employees, and agents from claims, liabilities, damages, losses, and reasonable costs arising from your use of the Service, your breach of these Terms, your content or instructions, your processing of personal data, or your use of the Service in violation of any third-party platform's terms or applicable law. This applies to consumers only to the extent permitted by law. --- ## **14. Suspension and termination** We may suspend or terminate access immediately for breach, non-payment, suspected unlawful use, or where required by law or by a third-party platform. Either party may terminate for a material breach that remains uncured 30 days after written notice. We may also terminate if you become insolvent or subject to bankruptcy or similar proceedings. You may cancel at any time under Section 7. On termination, your right to use the Service ends; data handling on termination is described in Sections 10–11 and the Privacy Policy. Sections that by their nature should survive (including Sections 10–13, 16, 18 and 19) survive termination. --- ## **15. Changes to these Terms** We may update these Terms. For material changes we will give reasonable advance notice by email or in-product, effective on the stated date or at your next renewal. If you do not accept a material change, your remedy is to stop using the Service and cancel before it takes effect. We will not impose material changes on consumers without notice. --- ## **16. Governing law and disputes** These Terms are governed by the laws of **Estonia**. **If you are a consumer, you keep the protection of the mandatory laws of your country of residence and may bring proceedings in its courts where the law allows.** For business users, the courts of Tallinn, Estonia have exclusive jurisdiction. Please contact us at hello@fansly-api.com first so we can try to resolve any dispute. Consumers may also use the EU Online Dispute Resolution platform and national ADR bodies. Data-protection complaints may be made to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon) or your local supervisory authority. --- ## **17. Compliance with laws** You will comply with all applicable laws in using the Service, including export-control and economic-sanctions laws, and you represent that you are not located in, or acting for anyone in, a sanctioned territory or on a restricted-party list. --- ## **18. Affiliate and referral program** We may operate an affiliate or referral program under which we pay commissions or payouts to participants who refer customers to the Service, on the rates and terms we make available from time to time. We may change, suspend, or end the program at any time, and we may withhold or reclaim payouts in cases of fraud, abuse, chargebacks, or breach of these Terms. --- ## **19. General** If any provision is held invalid, the rest remains in effect. Our failure to enforce a provision is not a waiver. We are not liable for failure or delay caused by events beyond our reasonable control, including third-party platform changes, outages, or force majeure. We may assign these Terms to an affiliate or successor; you may not assign without our consent. We give notices by email or in-product. **Order of precedence:** in case of conflict, these Terms (including the data processing terms in Section 10 and the payment terms in Section 7) prevail, then the Privacy Policy, then the Cookies Policy. These documents are the entire agreement between us regarding the Service. --- ## **20. Contact** Fans Holdings OÜ — Pille tn 9/3-53, Kesklinna district, Tallinn, Harju County, 10138, Estonia. Email: **hello@fansly-api.com**. --- ### Model withdrawal form (consumers) *To Fans Holdings OÜ, hello@fansly-api.com: I hereby give notice that I withdraw from my contract for Fansly API. Ordered on: ____________ Name: ____________ Address: ____________ Date: ____________* --- ## Contact - Email: hello@fansly-api.com - Telegram: https://t.me/onlyfansapi_updates - Documentation: https://docs.onlyfansapi.com/api-reference/fansly - Sign up: https://www.fansly-api.com/register