For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Join Community
WelcomeDocsAPI ReferenceWebhooksChangelog
WelcomeDocsAPI ReferenceWebhooksChangelog
  • Introduction
    • Welcome
    • Quick Start
    • Testing Your App
  • App Store
    • Introduction
    • Listing Requirements
    • App Subscriptions
    • Deeplinks
  • Authentication
    • Overview
    • Quick Start
    • Implementation Guide
    • Scopes
    • Rate Limits
    • Working With Rate Limits
  • Versions
    • Overview
    • Management Strategies
  • Build With AI
    • Docs For Your LLM
  • Tutorials
    • Example Chatbots
    • Multipart Media Upload
    • Sending Mass Messages
    • Security
  • Integrations
    • n8n
LogoLogo
Join Community
On this page
  • You must be a KYC-verified creator
  • Pre-approval is open now — public listings and billing are coming soon
  • What can be listed
  • Apps must be SFW in presentation
  • The App Store journey
  • Next steps
App Store

App Store Introduction

An overview of the Fanvue App Store — what it is, who can build for it, and how an app goes from idea to listed.

Was this page helpful?
Previous

App Store Listing Requirements

Requirements for being listed — and remaining listed — in the Fanvue App Store.

Next
Built with

The Fanvue App Store is a marketplace of creator-built apps that other creators on Fanvue can discover, install, and use. If you’re a developer or a technical creator, the App Store is how you put your tooling in front of thousands of Fanvue creators — whether that’s automation for messaging, analytics dashboards, content workflows, fan-facing experiences, or something nobody has built yet.

This section of the docs walks you through everything you need to build and publish an app.

You must be a KYC-verified creator

Access to the Builder area and the App Store is available only to Fanvue users who are registered as creators and have completed KYC (identity verification). Fans cannot create apps, manage OAuth credentials, or publish listings.

See the Quick Start prerequisites for full setup requirements before you begin.

Pre-approval is open now — public listings and billing are coming soon

The App Store is rolling out in phases. Today you can build your app and submit it for pre-approval — a full review against the policy described in these docs, ending in an Approved or Rejected decision. Two pieces are still on the way:

  • Public App Store listings — approved apps don’t yet appear on the App Store for other creators to browse or install. Once listings launch, already-approved apps will go live.
  • Fanvue payment rails — the billing infrastructure for paid apps is coming soon. Paid embedded apps can still pre-approve under the policy.

Off-platform apps are unaffected and operate normally today.

What can be listed

The App Store is intentionally broad about the kinds of apps it accepts. Apps generally fall into categories like:

  • Creator tooling — dashboards, analytics, scheduling, bulk messaging, content management.
  • Automation — workflows that run on webhooks or schedules to save creators manual work.
  • Fan-facing surfaces — embedded experiences that creators can add to their posts or chats for their fans to interact with.
  • Integrations — bridges between Fanvue and third-party services (CRMs, email tools, AI providers, etc.).
  • Off-platform tools — apps that live entirely outside Fanvue’s UI but use the Fanvue API.

Apps that take payment must be embedded and listed on the App Store — Fanvue payment rails are only available to embedded apps. See App Types for the full rules.

Apps must be SFW in presentation

An app’s listing, UI, marketing materials, screenshots, and notifications must remain SFW. Apps may be tools that creators use to manage or interact with adult content on Fanvue — but the app itself must not display or promote NSFW content in its own presentation layer. See Listing Requirements for the full content rules.

The App Store journey

At a high level, publishing an app looks like this:

  1. Create your app in the Builder area. This generates OAuth credentials (Client ID and Client Secret).
  2. Bootstrap your codebase — start from the Fanvue App Starter template or roll your own setup. See the OAuth Quick Start for the starter walkthrough.
  3. Save your client secret immediately and wire it into your OAuth flow. The secret is shown only once on creation. See Managing your OAuth client secret for lifecycle and rotation guidance.
  4. Define your app type — embedded or off-platform. Embedded apps also configure their app surfaces (the places they appear inside Fanvue, such as creator settings, posts, or chat).
  5. [Optional] Configure webhooks to receive platform events — see the Webhooks reference.
  6. [Optional] Configure pricing if your app is paid. Paid apps must use Fanvue’s payment rails (coming soon — see above).
  7. Configure your store listing — logo, name, tagline, description, preview images, and test credentials for reviewers.
  8. Submit for pre-approval. Your app is reviewed against the policy and receives an Approved or Rejected decision. Once public App Store listings launch (coming soon — see above), approved apps go live automatically. See Publishing Your App for the full submission and review flow.

Next steps

  • App Types — the differences between embedded and off-platform apps, and how listing interacts with Fanvue payment rails.
  • Publishing Your App — required fields, submission process, review outcomes, and app states.
  • Listing Requirements — the full policy baseline your app must meet to be listed and remain listed.
  • OAuth Implementation Guide — technical details for integrating with Fanvue’s OAuth 2.0 flow.