Use the Fanvue API from Python with plain requests

Set up the client

All you need is the requests library and your CreatorAPI key in the X-API-Key header. Keep the key in an environment variable, never in code, and reuse one session so the header rides along on every call.

# pip install requests
import os, requests

BASE = "https://api.creator-api.com"
session = requests.Session()
session.headers["X-API-Key"] = os.environ["CREATOR_API_KEY"]

account = os.environ["CREATOR_ACCOUNT_ID"]  # the Fanvue creator id you get when you connect an account

Read subscribers

Subscribers come back as structured JSON from one GET request, pulled straight from Fanvue's official API. Every native route follows the same pattern: /v1/{account}/native/{path}, and each read costs 1 credit.

# list subscribers for a connected Fanvue creator
r = session.get(
    f"{BASE}/v1/{account}/native/creators/{{creator_uuid}}/subscribers",
)
r.raise_for_status()
print(r.json())

Read insights and everything else

Earnings, spending, top spenders, chats, posts and vault media are all reads on the same route pattern, so one helper covers the whole surface. The exact paths for all 147 official Fanvue routes are listed in the Fanvue API reference.

def native_get(path, **params):
    # works for any read path from the reference: earnings, insights, chats, posts
    r = session.get(f"{BASE}/v1/{account}/native/{path}", params=params)
    r.raise_for_status()
    return r.json()

Start a data export

A single POST starts a bulk export of subscribers, earnings, chats or posts to CSV or JSONL. One export job costs 10 credits, and you download the file when the job is done.

# export all earnings to CSV, 10 credits per job
job = session.post(
    f"{BASE}/v1/{account}/exports",
    json={"dataset": "earnings", "format": "csv"},
)
job.raise_for_status()
print(job.json())

Webhooks and errors

Fanvue's own native webhook subscriptions push events straight from Fanvue, and CreatorAPI's unified layer, signed with HMAC SHA256 and retried with backoff, normalises events across every platform you connect. The quickstart walks through signature verification. Errors are plain HTTP: 401 for a bad key, 402 when credits run out, 429 on rate limits, always with a JSON body of {"error": "..."}, so raise_for_status() plus one except block covers you.

Or let an AI write the Python for you

The whole API fits in one file made for language models. Paste it into Claude or Codex and describe what you want; the model writes the calls.