Use the Fansly API from Python with plain requests

Set up the client

All you need is the requests library and your API 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 Fansly creator id you get when you connect an account

Read subscribers

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

# list the newest 50 subscribers
r = session.get(
    f"{BASE}/v1/{account}/native/subscribers",
    params={"limit": 50},
)
r.raise_for_status()
print(r.json())

Read earnings without doing mills math

Fansly's own apiv3 reports money in mills, thousandths of a dollar, and keeps 20 percent of every sale. CreatorAPI adds a computed USD sibling field, such as totalNetUsd, to every money value so your Python reads a plain dollar amount.

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

earnings = native_get("account/wallets/earnings")
print(earnings["totalNetUsd"])

Start a data export

A single POST starts a bulk export of subscribers, transactions, 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 subscribers to CSV, 10 credits per job
job = session.post(
    f"{BASE}/v1/{account}/exports",
    json={"dataset": "subscribers", "format": "csv"},
)
job.raise_for_status()
print(job.json())

Webhooks and errors

Webhook deliveries are signed with HMAC SHA256 and retried with backoff, so your Python service can trust what arrives and verify it in a few lines. 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.