Connecting the client - onlyfanskit

Most production integrations do not construct an OnlyFans client with raw session material. You connect on the hosted API, keep the account id, and call methods over HTTP:

curl "https://api.onlyfanskit.dev/v1/accounts/$ACCOUNT_ID/users/me" \
  -H "Authorization: Bearer $OFK_KEY"

The SDK powers that passthrough and documents every method and type. Use API reference and SDK resources for request shapes; use the REST surface to execute calls.

When you use the SDK directly

The typed client is for runtimes that execute against OnlyFans with a session already provisioned on onlyfanskit infrastructure (internal services, advanced automation). It requires the same session fields the platform stores after a successful connect:

import { OnlyFans } from "onlyfanskit";

const of = new OnlyFans({
  cookie: "<session-cookie>",
  xBc: "<x-bc>",
  userId: "123456789",
  userAgent: "<stable-user-agent>",
});

Option	Description
`cookie`	Session cookie for the connected account.
`xBc`	`x-bc` value for the account.
`userId`	Numeric OnlyFans user id.
`userAgent`	Stable user agent per account.
`fetch`	Optional transport override.

If you are building on onlyfanskit.dev, you should not extract cookies from a browser or import cURL. Use embedded connect or email + password and act on the returned account id.

Keeping a session healthy

When a session expires, start a new connect attempt or reauthenticate the account on the hosted API, then continue calling with the same account id. See Handling errors for session and upstream failures.