CreatorAPI is a hosted REST API for Fansly that returns plain JSON. Call it with fetch from Node, Bun or Deno: one key, one header, no SDK to install.
You do not need an SDK because CreatorAPI is plain REST that returns JSON, so any HTTP client in any JavaScript runtime works: fetch, axios, got, undici, whatever you already use. Fansly itself publishes no official public API. CreatorAPI fills that gap by calling the same apiv3 endpoints the Fansly app uses, through your own connected session, so responses are stable, structured JSON instead of scraped HTML. The examples below use the built in fetch that ships with Node 18 and later.
Listing subscribers takes one GET request with your key in the X-API-Key header. Every native route follows the same pattern, so once this works, fans, messages, earnings, posts and transactions work the same way.
// list the newest 50 subscribers · a native read costs 1 credit const res = await fetch( "https://api.creator-api.com/v1/{account}/native/subscribers?limit=50", { headers: { "X-API-Key": process.env.CREATOR_API_KEY } } ); const subscribers = await res.json();
Fansly's own apiv3 reports money in mills, thousandths of a dollar. CreatorAPI adds a computed USD sibling field to every money value, so your JavaScript reads a plain number.
// earnings.totalNetUsd is already dollars, no /1000 needed const res = await fetch( "https://api.creator-api.com/v1/{account}/native/account/wallets/earnings", { headers: { "X-API-Key": process.env.CREATOR_API_KEY } } ); const earnings = await res.json(); console.log(earnings.totalNetUsd);
Push instead of poll, handle failures cleanly, and let your AI editor write the boring parts.
Register a URL with POST /v1/{account}/webhooks and CreatorAPI pushes events like new messages, tips, subscriptions and payouts. Every delivery is signed with HMAC SHA256 and retried with backoff. Details on the Fansly webhooks page.
Failures come back as JSON with a clear error field. 401 means a bad key, 402 insufficient credits, 429 rate limit, so a try catch plus a status check covers it.
The whole API reference ships as one file, llms-full.txt. Paste it into Claude or Codex and let the assistant write your integration against real routes.
The fastest path is the quickstart, which takes you from signup to your first JSON response in a few minutes. For the full route catalog, 97 live verified GET routes plus writes across 15 categories, see the Fansly API overview. The free trial includes 1,000 credits with no card required, and a native read costs 1 credit, so there is plenty of room to prototype.
Fansly publishes no official public API. CreatorAPI fills that gap with a hosted REST API that any JavaScript runtime can call, using the same apiv3 endpoints the Fansly app uses through your own connected session.
No. CreatorAPI is plain REST returning JSON, so fetch, axios, got or any other HTTP client works as is.
Yes. Any runtime with an HTTP client can call it. The examples on this page use the built in fetch that ships with Node 18 and later.
Send your key in the X-API-Key header on every request. Keys look like ca_live_ and you get one after connecting an account.
Yes. Fansly reports money in mills, but CreatorAPI adds a computed USD sibling field to every money value, so your code reads a plain number.
The free trial includes 1,000 credits with no card required, and a native read costs 1 credit. The Fansly plan is 39 USD per month with 24,000 credits.
Yes. The full API reference ships as one file, llms-full.txt, which you can paste into Claude or Codex so the assistant codes against real routes.
Start free with 1,000 credits, no card, one key for every platform you connect.