Fans, spend, history, notes, lists, and segments are all endpoints. Build the exact CRM your agency runs on, synced live instead of copied from screenshots.
# pull a fan's lifetime spend for your CRM curl https://api.fanduit.co/v1/accounts/$id/fans/9021/spending \ -H "Authorization: Bearer sk_live_…" → 200 OK { "total": 842.50, "tips": 120, "ppv": 722.5 }
The data layer for a creator CRM.
List all, active, expired, and latest fans with subscribe dates and status.
Per-fan lifetime spend, purchases, tips, and full subscription history.
Read and write your own notes on any fan to keep context with your team.
Create fan lists, add and remove members, and tag fans with labels.
Housekeeping generates VIP, win-back, new, and silent segments for you.
Export the whole CRM as JSON or CSV whenever you want.
Read fans, enrich, act.
List fans and their spend and status.
Add notes, labels, and list membership.
Message a segment or sync it to your own tools.
Custom, not off-the-shelf.
Build the fan view your team actually needs instead of adapting to a closed UI.
Rank fans by spend and surface the top ones for personal attention.
Act on win-back and silent segments with targeted campaigns.
Push fan data into your warehouse or existing CRM via webhooks.
Run a whole roster from one API — connect every creator you operate and automate messaging, growth, and reporting at scale.
Neutral infrastructure on accounts you own, with encrypted credentials, per-account proxies, and no screen sharing.
Clean REST + MCP, signed webhooks, idempotency, and transparent credit metering. Build tools that don\'t break by morning.
It is the API you build a CRM on. You get fans, notes, lists, and segments as endpoints and build the interface you want.
Yes, the fan endpoints resolve per account, so the same CRM covers both platforms.
Yes, through the API directly or bulk export jobs in JSON and CSV.
Start with real fan data on the API.