---
title: "Connect Login"
method: POST
path: "/v1/connect/login"
---

# Connect Login

`POST /v1/connect/login`

## Request

- Base URL: `https://creator-api.com` (the document declares no server; this is the origin it was published from)
- URL: `https://creator-api.com/v1/connect/login`
- Auth: none declared

Connect a customer's own account by direct login (identifier + password), for
platforms whose native login is a plain request with no hosted-browser session
needed. Currently: 4based only · OnlyFans/Fansly use POST /v1/connect/session
(hosted browser) instead, so we never see those passwords. Here the password IS
sent to us once, used in-process to exchange it for a session token via the
platform's own login endpoint. By default it is then discarded · never logged, never
stored. Optional `save_password: true` (opt-in, default off) keeps an ENCRYPTED copy
(see of_4based_vault) so the automatic token-refresh job can re-log-in on the
customer's behalf if 4based ever rejects the session, instead of the account going
dark until they manually reconnect. Purged immediately on disconnect
(DELETE /v1/accounts/{creator_id}).

## Headers

- `x-api-key` string, nullable
- `authorization` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/creator-api/apis/creatorapi.md) · [All operations](https://skmtc.dev/creator-api/apis/creatorapi/llms.txt) · [OpenAPI document](https://skmtc.dev/creator-api/apis/creatorapi/revisions/530fde3d35cf?raw)