What creators see
Approve access once
The first time they open your app, Fanvue shows a consent screen listing exactly what your app can do (the scopes you requested). One approval covers everything.
Why build an embedded app?
- Distribution — your app is listed on the App Store in front of the whole Fanvue creator base.
- Zero-friction sign-in — Fanvue tells your app who the creator is. No registration forms, no passwords, no drop-off between “installed” and “using it”.
- Work on the creator’s behalf — with the creator’s one-time consent, your app gets full API access to act for them, even in the background after they’ve closed the app.
- Feels native — Fanvue tells your app the creator’s active light/dark theme, so your app can match the surrounding platform and feel like a built-in part of Fanvue.
- Get paid through Fanvue — embedded apps on the App Store can charge creators through Fanvue’s payment rails, so billing is handled for you. See App Subscriptions.
How it works (the short version)
Your app runs in an iframe inside Fanvue. When a creator opens it, Fanvue passes your page a short-lived token that proves “this creator is using your app inside Fanvue right now.” Your server swaps that token for standard OAuth credentials and can then call the Fanvue API as that creator. Our@fanvue/builder-sdk SDK handles that whole exchange for you — most apps add a couple of files and authentication just works.
Build your embedded app
The step-by-step integration guide: register your app, drop in the SDK, and call the Fanvue API on the creator’s behalf.
Learn more
App Types
Embedded vs off-platform apps, and the rules for listing and pricing each.
Publishing Your App
Get your app reviewed and live on the App Store.
App Subscriptions
Charge creators for your app through Fanvue’s payment rails.
Credentials & Scopes
Client IDs, secrets, and the permissions your app can request.