Use the 4Based 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 4based creator id you get when you connect an account

Read subscribers by shorthand

Subscribers come back as structured JSON from one GET request. 4based buries the creator's own id in almost every path, so CreatorAPI gives you a shorthand instead: subscribers resolves to the real path and fills in the id for you.

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

Read earnings and everything else

Earnings, tiers, chats, feed and vault are all reads on the same route pattern, so one helper covers the whole 4based surface. The exact shorthands and raw paths are listed in the 4Based API reference.

def native_get(path, **params):
    # works for any read shorthand: me, subscribers, tiers, chats, feed, vault, earnings
    r = session.get(f"{BASE}/v1/{account}/native/{path}", params=params)
    r.raise_for_status()
    return r.json()

# earnings for a date range
earnings = native_get("earnings", init_from="2026-01-01", init_to="2026-07-01")

Start a data export

A single POST starts a bulk export of subscribers or chats 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 working calls.