CreatorAPI exports subscribers, chats and vault media from 4based in bulk, the same way it already does for OnlyFans and Fansly. One API call creates the job, you download the file when it is done.
You can export the two bulk datasets 4based exposes today, subscribers and chats, each as CSV or JSONL, plus a linked listing of vault media. 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 authenticated endpoints the 4based app uses, so you get complete, structured records rather than scraped fragments.
Every fan on the account with their subscription and tier details. The full list, not a paginated slice.
Conversation and message history across threads. Useful for QA, training data and compliance archives.
A clean inventory of what is sitting in the creator's media vault, ready to pair with your own storage.
Pull earnings stats for a date range alongside the export to reconcile revenue against activity.
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 4based subscribers as CSV, costs 10 credits
curl -X POST \
-H "X-API-Key: $CREATOR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"dataset": "subscribers", "format": "csv"}' \
"https://api.creator-api.com/v1/{account}/exports"
Teams use exports to seed data warehouses, hand chat history to QA, 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.
Pair a subscriber export with an earnings pull instead of screenshotting the 4based dashboard.
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 your vault listing that belongs to you, independent of the 4based dashboard.
Because an export job returns complete, structured data in one pass, while copying screens by hand is slow and error prone, and 4based has no large third party scraper ecosystem to fall back on either. CreatorAPI calls the same authenticated endpoints the 4based 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 and Fansly, so all three export 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.
Subscribers and chats as bulk datasets, each exportable as CSV or JSONL. Vault media is available through the same export job as a linked file listing.
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, 4based publishes no official public API, the same as OnlyFans and Fansly. CreatorAPI fills that gap by calling the same authenticated endpoints the platform app uses, through your own connected session.
No. CreatorAPI reads the native platform endpoints through your connected account session, so exports contain complete structured records instead of scraped page fragments.
Yes. One key covers all three platforms and the exports endpoint follows the same pattern for OnlyFans, Fansly and 4based accounts.
Start free with 1,000 credits, connect a 4based account and run your first export in minutes.