CreatorAPI exports subscribers, transactions, chats and posts from Fansly in bulk. One API call creates the job, you download the file when it is done.
You can export four bulk datasets: subscribers, transactions, 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 comes from the same apiv3 endpoints the Fansly app itself uses, so you get complete, structured records rather than scraped fragments.
Every fan on the account with their subscription details. The full list, not a paginated slice.
The account's wallet transactions as one bulk file, in the same mills based amounts Fansly itself uses. The raw material for financial analytics and bookkeeping.
Message history across chatrooms and direct messages. Useful for QA, training data and compliance archives.
The account's post and story 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 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 transactions as CSV, costs 10 credits
curl -X POST \
-H "X-API-Key: $CREATOR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"dataset": "transactions", "format": "csv"}' \
"https://api.creator-api.com/v1/{account}/exports"
Teams use exports to seed data warehouses, hand transactions 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 a transactions CSV instead of screenshots. Remember Fansly reports money in mills, not cents, so divide raw amounts by 1000, or use the computed USD sibling fields CreatorAPI adds automatically.
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 what Fansly retains in your account.
Because an export job returns complete, structured data in one pass, while scraping and manual copying are slow and brittle. CreatorAPI is not a scraper: it calls the same apiv3 endpoints the Fansly app itself uses through your own connected session, so the output is stable JSON turned into clean CSV or JSONL. The same key also covers OnlyFans, 4based and Fanvue, so every platform exports through one identical endpoint pattern.
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, transactions, chats and posts. 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.
No, Fansly publishes no official public API. CreatorAPI fills that gap by calling the same apiv3 endpoints the Fansly app itself uses, through your own connected session.
No. CreatorAPI reads the native Fansly apiv3 endpoints through your connected account session, so exports contain complete structured records instead of scraped page fragments.
Yes. One key covers OnlyFans, Fansly, 4based and Fanvue, and the exports endpoint follows the same pattern on every connected platform.
Start free with 1,000 credits, connect an account and run your first export in minutes.