Skip to main content
Every Fanvue app starts as an OAuth client and grows only the parts you need. Use the table to see which parts apply to your app, then build them in the order below. If you haven’t created an app yet, start with Build your first Fanvue app.

​
What an app is made of

The app type decides which parts are open to you. An API-only app is just an OAuth client that creators connect to; it never appears in the App Store. An off-platform app adds an App URL, so creators open it on your own site. An on-platform app loads inside Fanvue, on a creator surface and optionally a fan surface.

​
Build order

  1. Create the app and get a token with Build your first Fanvue app.
  2. Pick a type. Choose your app type compares the three and covers switching.
  3. Add the Builder SDK. @fanvue/builder-sdk wraps OAuth, sessions, the API client and webhook verification for each app type; see the Builder SDK overview. @fanvue/ui provides the components Fanvue itself is built with; see the UI Library.
  4. Receive events. Webhooks arrive in four event families: Creator, Checkout, App and Legacy.
  5. Publish fan experiences if your app is on-platform. Fans can pay the creator inside an experience. See Fan experiences.
  6. Move settings into a manifest. An App Manifest is an app-manifest.json file on your app domain that declares your type, URLs, scopes, redirect URIs and webhooks.
  7. Add billing. A listed app charges creators with pricing plans and one-time items at a Fanvue-hosted checkout, and you receive 80% of each charge. See App billing.
  8. Submit for review from App details. Review ends in approval or rejection, and an approved app appears on the App Store for creators to install. Listing copy and images must be safe for work, because creators see them before they open your app. See Submit your app for review and Listing requirements.