4based ships no official API. CreatorAPI reaches it natively and hands you shorthand aliases, so you never touch 4based tokens, headers or its path layout. Same key, same route pattern you already use for OnlyFans and Fansly, live today.
No. Like the OnlyFans API and the Fansly API, 4based has no official public API. CreatorAPI reaches all three through native endpoints, signing every request for you server side, so from your side it is one clean REST surface with one key.
4based puts the creators own id in almost every path, like /user/{id}/subscription. You never handle that. Call a shorthand and CreatorAPI rewrites it to the real path and fills in the id. It is the same me you already use on OnlyFans and Fansly.
# the creators 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/subscribers"
curl -H "X-API-Key: $CREATOR_API_KEY" \
"https://api.creator-api.com/v1/{account}/native/earnings"
4based joins the platforms you already run through CreatorAPI.
The same CreatorAPI key and the same /v1/{account}/native/{path} pattern cover OnlyFans, Fansly and 4based. No second integration to maintain.
Read me, subscribers, tiers, chats, feed, vault and earnings without knowing a single 4based path.
4based needs no residential proxy. Connect a captured session and read and write straight away.
Three steps, then call the same pattern you use everywhere else.
From a logged in 4based session you take three values: a token, a resource and an account id.
Post those three fields to the connect endpoint with a full scope key. The account is verified and attached to your key. No password touches CreatorAPI.
Use your CreatorAPI key against the same native route pattern, by shorthand or by raw path.
4based is a smaller platform than OnlyFans or Fansly, and support here is native, reached through a captured session rather than an official API. Reads cover profile, subscribers and counts, tiers, conversations and messages, feed, vault and earnings; writes cover sending messages and pay per view with a full scope key. ManyVids, MYM, JustForFans, LoyalFans and FanCentro are built and on the way.
No. 4based has no official public API. CreatorAPI reaches 4based through native endpoints, the same way it reaches OnlyFans and Fansly, behind one unified surface and one key.
Yes. 4based is live today through CreatorAPI, with reads and writes for profile, subscribers, tiers, conversations, messages, feed, vault and earnings.
No. CreatorAPI gives you shorthand aliases such as me, subscribers, tiers, chats, feed, vault and earnings, and fills in the creators own 4based id for you, so you never handle the path layout.
Import a captured 4based session, which is a token, a resource and an account id. No residential proxy is needed for 4based. The account is verified and attached to your key.
No. 4based is included in every CreatorAPI plan. A native read is one credit and a native write is two credits.
All three are native, since none of them ship an official public API. CreatorAPI reaches all three through the same native route pattern with the same key.
Start free with 1,000 credits, no card required.