Skip to main content
Every Fanvue integration is an app, and creating an app is simply how you get your API credentials. You never have to list it anywhere: a private script that only you run is still an app, and so is a tool you sell to thousands of creators. Same starting point, your choice of destination. So whether you just want a Client ID and Secret to call the API, or you want to build and sell a product to the whole Fanvue creator base, you are in the right place. Start small, go as far as you like.
You need a Fanvue creator account with completed KYC
Creating an app, managing OAuth credentials, and publishing listings are available only to users registered as creators who have completed KYC (identity verification). Fans cannot access these areas. See the Quick Start prerequisites for full setup requirements.

​
The journey

Three steps, and you can stop at any of them.
1

Create an app and get credentials

Create an app in the Fanvue Builder to get your Client ID and Client Secret, then pick the scopes it can use. This is all you need to start calling the API. See Credentials.
2

Build it your way

Decide whether your app runs inside Fanvue’s UI (embedded) or on your own infrastructure (off-platform). An off-platform app can be a private internal script, a tool for one client, or a public product, and it never needs a listing. See App Types.
3

List and monetize (optional)

When you want reach, list your app on the App Store so other creators can discover and install it, and charge for it through Fanvue’s payment rails. This is the final stop on the journey, not the price of admission.

​
Pick your starting point

I just want the API

Create an app, grab your Client ID and Secret, choose your scopes, and start making calls. No listing, no review, no payment setup.

I want to build a product

Render UI inside Fanvue, reach the whole creator base through the App Store, and bill for it through Fanvue. Start by choosing your app type.

​
Where the App Store comes in

The App Store is a marketplace of creator-built apps that other creators on Fanvue can discover, install, and use. Listing is how you put your tooling in front of thousands of creators: automation for messaging, analytics dashboards, content workflows, fan-facing experiences, or something nobody has built yet. It is the endpoint of the journey for builders who want distribution, not the definition of what an app is. Apps that take payment must be listed on the App Store. Once it’s listed, any app can offer paid plans billed through Fanvue’s payment rails, whether it’s embedded or off-platform. Off-platform apps can also skip listing and handle payment with their own processor. See App Types for the full rules.
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 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 apps can still pre-approve under the policy.
Off-platform apps are unaffected and operate normally today.
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.

​
Next steps

Credentials

Create your app, get your Client ID and Secret, and choose scopes.

App Types

Embedded vs off-platform, and how listing interacts with Fanvue payment rails.

Publishing Your App

Required fields, submission, review outcomes, and app states.

OAuth Implementation Guide

The authentication flow that powers every app, embedded or off-platform.