> ## Documentation Index
> Fetch the complete documentation index at: https://api.fanvue.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Embedded Apps

> An embedded app lets you embed your website into Fanvue, so creators can use your product without ever leaving the platform.

An **embedded app** lets you embed your website into Fanvue. Creators discover your app on the App Store, install it, and use it right inside Fanvue — no separate logins, no copying API keys, no leaving the platform.

If you already have a web app, you're most of the way there. Fanvue renders your existing site inside the platform and tells you which creator is using it, so you can skip building sign-up, login, and account-linking entirely.

## What creators see

<Steps>
  <Step title="Find your app on the App Store">
    Creators browse the App Store inside Fanvue and open your listing.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Use your app inside Fanvue">
    Your app opens inside the platform, already signed in as that creator. Next time, it opens straight away — no login screen, ever.
  </Step>
</Steps>

## 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](/docs/app-store/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](/docs/api-reference/overview) as that creator.

Our [`@fanvue/builder-sdk`](https://www.npmjs.com/package/@fanvue/builder-sdk) SDK handles that whole exchange for you — most apps add a couple of files and authentication just works.

<Card title="Build your embedded app" icon="code" href="/docs/app-store/embedded-apps/integration-guide">
  The step-by-step integration guide: register your app, drop in the SDK, and call the Fanvue API on the creator's behalf.
</Card>

## Learn more

<CardGroup cols={2}>
  <Card title="App Types" icon="layer-group" href="/docs/app-store/app-types">
    Embedded vs off-platform apps, and the rules for listing and pricing each.
  </Card>

  <Card title="Publishing Your App" icon="rocket" href="/docs/app-store/publishing-your-app">
    Get your app reviewed and live on the App Store.
  </Card>

  <Card title="App Subscriptions" icon="credit-card" href="/docs/app-store/app-subscriptions">
    Charge creators for your app through Fanvue's payment rails.
  </Card>

  <Card title="Credentials & Scopes" icon="key" href="/docs/app-store/credentials">
    Client IDs, secrets, and the permissions your app can request.
  </Card>
</CardGroup>