Skip to main content
This is where every Fanvue integration begins. Creating an app gives you the Client ID and Client Secret you use to authenticate and the scopes that decide what your app can touch. Whether you are wiring up a private script or building a product for the App Store, you start here.
You need a Fanvue creator account with completed KYC
Creating an app and managing OAuth credentials are available only to users registered as creators who have completed KYC (identity verification). Fans cannot access the Builder area. See the Quick Start prerequisites.

​
Create an app

The Fanvue Builder (the Developer area) is where you create apps and manage their credentials. Creating an app takes a few minutes.
1

Open the Builder area

Sign in to Fanvue with your KYC-verified creator account and open the Builder (Developer area), then create a new app.
2

Get your Client ID and Client Secret

Fanvue generates a Client ID (a public identifier) and a Client Secret (a server-side credential that authenticates your backend to Fanvue’s token endpoint).
The Client Secret is shown only once, at the moment the app is created. Fanvue does not store it in retrievable form. Copy it into your secrets manager (or .env.local as OAUTH_CLIENT_SECRET) before leaving the page. If you lose it, your only option is to regenerate, which is a breaking change. See Managing your OAuth client secret.
3

Add your redirect URI

Register the redirect URI Fanvue sends users back to after they authorize. It must match your app exactly, including the HTTPS protocol and port. For the Fanvue App Starter, use https://my-fanvue-app.dev:3001/api/oauth/callback in development and https://YOUR_DOMAIN/api/oauth/callback in production.
4

Choose your scopes

Select the scopes your app can request. They must match the scopes your code asks for (in the starter, OAUTH_SCOPES). Stick to the minimum your app needs. See Scopes below.
On first connection users authorize through Fanvue’s standard OAuth 2.0 flow, and you receive time-limited access tokens to call the API on their behalf. See the Authentication Overview and OAuth Quick Start for the full walkthrough.

​
Choose your scopes

Scopes are the permissions that control what your app can do once a user connects it. Every API request is checked against your token’s scopes; a request without sufficient scopes returns 403 Forbidden. Request only what your app actually needs, and remember users see the permissions you ask for when they connect.
ResourceScopes
Userread:self
Chatread:chat, write:chat
Fanread:fan
Creatorread:creator, write:creator
Mediaread:media, write:media
Postsread:post, write:post
Insightsread:insights
Tracking Linksread:tracking_links, write:tracking_links
Agencyread:agency, write:agency
The scopes you select in the Builder must exactly match those your code requests. A mismatch is a common cause of authorization errors. For per-scope descriptions and setup details, see Scopes.

​
Optional configuration

Depending on what you are building, your app may also configure:
  • Webhooks, to receive platform events. Configure them in the Events tab of your app in the Developer area. See Webhooks.
  • Pricing, if your app is paid. Paid apps must be embedded and use Fanvue’s payment rails (coming soon). Plan UUIDs appear in the Pricing tab of your app. See App Types.

​
Next steps

OAuth Quick Start

Wire your Client ID, Secret, and scopes into a working Next.js app.

App Types

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

Implementation Guide

Token exchange, refresh, and secret lifecycle in depth.

Test your app safely

Set up a test creator account so development never touches your real profile.