4based does not publish an official public API. There is no developer portal and no documented endpoints, so every 4based integration is built on the same authenticated endpoints the 4based site itself uses. CreatorAPI hosts that access for you and exposes it as one clean REST surface, the same key and route pattern you already use for OnlyFans and Fansly.
4based puts the creator's own id in almost every path, for example /user/{id}/subscription. CreatorAPI fills that id in for you, so you call a shorthand and it rewrites to the real path. The shorthands are me, subscribers, subscriber-count, tiers, chats, feed, vault and earnings, the same me you already use on OnlyFans and Fansly.
# the creator's own profile, subscribers and earnings, by shorthand
curl -H "X-API-Key: $CREATOR_API_KEY" \
"https://api.creator-api.com/v1/{account}/native/me"
curl -H "X-API-Key: $CREATOR_API_KEY" \
"https://api.creator-api.com/v1/{account}/native/earnings"
Connecting a 4based account means importing a captured session, which is a token, a resource and an account id. No residential proxy is required for 4based, unlike OnlyFans and Fansly. The full route list is in the 4Based API reference.
The same three things developers build on OnlyFans and Fansly work on 4based, and CreatorAPI ships first party features for each.
4based is included in every CreatorAPI plan at no extra charge. A native read costs 1 credit and a native write costs 2, and you can start free with 1,000 credits and no card. Full details are on the pricing page.
Create a free key, connect a 4based account, and make one native GET call to me. From there the 4Based reference documents every route, and the same integration already covers OnlyFans, Fansly and Fanvue on the one key.
Start free with 1,000 credits, no card required. One key covers 4based, OnlyFans, Fansly and Fanvue.