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, lists, vouchers, payout and earnings without knowing a single 4based path.
4based needs no residential proxy. Connect a captured session and read and write straight away.
The easy way is one call. An advanced import path exists too, for a session you already captured yourself.
4based's own login is a plain request, no hosted browser needed. Send the creator's email and password once, CreatorAPI exchanges it for a session token. Discarded by default, or kept encrypted if you opt into automatic reconnect.
Already have a token, resource and account id from your own capture tooling? Post those three fields to the connect endpoint instead. No password touches CreatorAPI either way.
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 signed in session rather than an official API. Reads cover profile, subscribers and counts, tiers, conversations and messages, feed, vault, earnings, payouts, fan lists, recent interactions and per fan notes; writes cover sending messages and pay per view, per chat price overrides, pinning and read status, following and blocking, fan list management, voucher redemption and publishing scheduled posts, all with a full scope key. Two things by design stay out of scope: 4based's own account settings and payment details, and its raw session tokens, since exposing either would go beyond business data. ManyVids, MYM, JustForFans, LoyalFans and FanCentro are built and on the way.
Ten focused pages, one for each way people put native 4based access to work.
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, earnings, payouts, fan lists, follows, blocks and vouchers.
No. CreatorAPI gives you shorthand aliases such as me, subscribers, tiers, chats, feed, vault, lists, vouchers, payout and earnings, and fills in the creators own 4based id for you, so you never handle the path layout.
Sign in with the creator's 4based email and password, no hosted browser needed. Already have a captured session instead, a token, a resource and an account id? Import that directly. Either way, no residential proxy is needed and no password touches CreatorAPI unless you explicitly opt into automatic reconnect.
4based has its own plan at $39 a month, and comes bundled free with the Suite and Agency plans alongside OnlyFans and Fansly. A native read is one credit and a native write is two credits on any plan.
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.