CreatorAPI exports subscribers, earnings, chats and posts from Fanvue in bulk, pulled through the official Fanvue API. One API call creates the job, you download the file when it is done.
You can export four bulk datasets: subscribers, earnings, chats and posts, each as CSV or JSONL. CSV drops straight into a spreadsheet or accounting tool, JSONL streams line by line into a warehouse or script. The data is pulled through Fanvue's own official API, so you get complete, structured records rather than anything scraped or reconstructed.
Every fan on the account with subscription state. The full list, not a paginated slice.
The account's earnings as one bulk file. The raw material for financial analytics and bookkeeping.
Message history across conversations, including mass message campaigns. Useful for QA and compliance archives.
The account's post catalog with its metadata. A clean inventory of what has been published.
You create an export job with one POST request, then download the finished file. Each job costs a flat 10 credits regardless of dataset size.
POST to the exports endpoint with the dataset and format you want. The API returns a job you can check on.
CreatorAPI pulls the full dataset through the official Fanvue API in the background. You poll the job or just come back later.
When the job is done you download the CSV or JSONL file and load it wherever you need it.
One POST request starts the job.
# export all earnings as CSV, costs 10 credits
curl -X POST \
-H "X-API-Key: $CREATOR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"dataset": "earnings", "format": "csv"}' \
"https://api.creator-api.com/v1/{account}/exports"
Teams use exports to seed data warehouses, hand earnings to accounting, migrate to a new CRM, and keep offline backups.
Backfill your warehouse with JSONL history in one job, then keep it current with webhooks and incremental reads.
Hand your bookkeeper an earnings CSV instead of screenshots. Pair it with the financial analytics page for the full picture.
Moving to a new CRM or agency stack? Export subscribers and chats once and import them on the other side.
Keep an offline copy of chats and posts that belongs to you, independent of the Fanvue dashboard.
Because bundling four datasets into one downloadable file, in the same shape as your OnlyFans and Fansly exports, saves you from writing four separate pagination loops against Fanvue's official endpoints and reconciling the output format yourself. CreatorAPI still calls the real Fanvue API underneath, through your own OAuth connection, so the numbers match what Fanvue itself reports.
Create an export job with a POST request to the CreatorAPI exports endpoint, then download the finished CSV or JSONL file. Each export job costs a flat 10 credits.
Four bulk datasets: subscribers, earnings, chats and posts, pulled through the official Fanvue API. Each one can be exported as CSV or JSONL.
CSV and JSONL. CSV fits spreadsheets and accounting tools, JSONL fits warehouses and scripts that process records line by line.
One export job costs 10 credits regardless of dataset size. The free trial includes 1,000 credits with no card required, so you can run your first exports for free.
Yes. Fanvue publishes an official developer API, and CreatorAPI pulls the underlying records through it, then bundles them into one downloadable file.
Yes. One key covers every connected platform and the exports endpoint follows the same pattern everywhere, even though OnlyFans and Fansly are reached through native endpoints rather than an official API.
Start free with 1,000 credits, connect a Fanvue account and run your first export in minutes.