Connect an account

Connect paths

Embedded connect

Recommended for apps. Hosted popup or iframe — the creator signs in without you handling credentials.

Recommended for automation. Start a login, poll until it resolves, handle SMS / authenticator / email challenges.

Creator approves on their own device — no password in your stack.

Which should I use?

You are building…	Use
A dashboard, SaaS, or in-product onboarding	Embedded connect
A backend job, script, or agency tool with credentials	Email + password
A flow where the creator never shares a password	Mobile / QR

Cookie paste and cURL import are not supported on the public platform. Use one of the paths above so sessions stay on onlyfanskit infrastructure.

One-shot vs poll

Path	Pattern
Embedded / mobile	`POST /v1/connect/client-sessions` or `POST /v1/connect/login` with `auth_type: "mobile_app"` → poll until `completed_success`
Email + password	`POST /v1/connect/login` → poll → optional `PUT` for challenge codes

Success shape:

{
  "account": { "id": "acct_...", "ofUserId": "123", "state": "active" },
  "probe": { "id": 123, "username": "creator" }
}

Challenges (SMS, TOTP, email device verification) are documented in Two-factor & challenges.

Connecting requires the accounts:write scope and counts against your org’s connect-attempt rate limit.