> ## 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.

# Welcome to the Fanvue API

> Build on Fanvue: connect your tools, automate your workflow, and operate creator accounts through one API.

The Fanvue API gives you and your tools direct access to a creator's account: chats, posts, media, subscribers, insights, and more. Creators automate routine work, and agencies run operations across every creator they manage, all through OAuth 2.0 (no API keys).

<Info>
  **Looking for an API key?** Fanvue does not use them. Access is through OAuth 2.0: a user authorizes your app and you receive a short-lived **access token**, which you send as a `Bearer` token on each request. The fastest way to prove your access works is the [first call](/docs/introduction/first-call). To build a "Login with Fanvue" app, follow the [OAuth Quick Start](/docs/introduction/quick-start).
</Info>

<Note>
  ##### You need a Fanvue creator account with completed KYC

  Creating apps, managing credentials, and publishing to the App Store is available only to users registered as **creators** who have completed **KYC** (identity verification, the check that confirms who you are). Fans do not have access to these areas. If you don't have a creator account yet, sign up at [fanvue.com](https://www.fanvue.com) and complete KYC first.
</Note>

## What you can build

* Sync subscribers into your CRM, or pull earnings and insights into your own dashboards.
* Automate fan engagement: draft and send replies, run mass messages to a segment.
* Manage content programmatically: create, schedule, and pin posts; upload and grant media.
* Agencies: do all of the above across every creator you manage, from one connection.

Prefer no code? Connect the [MCP copilot](/docs/mcp-server) and drive your account from Claude in plain language.

## How it works

Users authorize your app through OAuth 2.0 and you receive a time-limited access token (a Bearer token) to call the API on their behalf. You only get the scopes the user grants. See [Authentication](/docs/authentication/overview) for the full flow.

## Start here

<CardGroup cols={3}>
  <Card title="Make Your First Call" icon="bolt" href="/docs/introduction/first-call">
    One authenticated request in five minutes.
  </Card>

  <Card title="OAuth App Quick Start" icon="key" href="/docs/introduction/quick-start">
    Build a working app from the starter template.
  </Card>

  <Card title="New to APIs?" icon="circle-question" href="/docs/core-concepts/new-to-apis">
    Plain-language primer on the core concepts.
  </Card>
</CardGroup>