creator-api-com Connect API

openapi: 3.2.0
info:
  title: Creator Api Com Connect API
  version: '1.0'
  description: 'Operations tagged Connect across 2 of this provider''s published API definitions: creator-api-com-openapi.json, creator-api-com-openapi.json. Each path carries the servers of the definition it was published in.'
tags:
- name: Connect
paths:
  /v1/connect/import:
    post:
      summary: Connect Import
      description: 'Connect a customer''s own account by importing captured credentials.

        Native (onlyfans/fansly) need a residential proxy + a captured session;

        official platforms (instagram, x, tiktok, ...) just need a bearer access_token.

        Attaches the account to the calling key. See GET /v1/platforms for required fields.'
      operationId: connect_import_v1_connect_import_post
      parameters:
      - name: x-api-key
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Api-Key
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Connect
  /v1/connect/login:
    post:
      summary: Connect Login
      description: '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}).'
      operationId: connect_login_v1_connect_login_post
      parameters:
      - name: x-api-key
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Api-Key
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Connect
  /v1/connect/session:
    post:
      summary: Connect Session Start
      description: 'Start a hosted-browser login ("Connect with OnlyFans/Fansly"). Returns a live-view

        `iframe_url` the customer logs into on the REAL platform (their own password + 2FA,

        we never see them) and a `session_id` to poll with POST /v1/connect/session/{id}/complete.

        The login runs behind the account''s managed proxy so its IP matches later API calls.

        Native only · official platforms use bearer tokens and need no browser.'
      operationId: connect_session_start_v1_connect_session_post
      parameters:
      - name: x-api-key
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Api-Key
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Connect
  /v1/connect/session/{session_id}/complete:
    post:
      summary: Connect Session Complete
      description: 'Poll a hosted-browser login. Returns {"status":"pending"} while the customer is

        still logging in, and {"status":"connected","verified":true,...} once the session is

        captured, verified and attached to your key.'
      operationId: connect_session_complete_v1_connect_session__session_id__complete_post
      parameters:
      - name: session_id
        in: path
        required: true
        schema:
          type: string
          title: Session Id
      - name: x-api-key
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Api-Key
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Connect
  /v1/connect/session/{session_id}:
    delete:
      summary: Connect Session Cancel
      description: Abort a hosted-browser login and release the browser.
      operationId: connect_session_cancel_v1_connect_session__session_id__delete
      parameters:
      - name: session_id
        in: path
        required: true
        schema:
          type: string
          title: Session Id
      - name: x-api-key
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Api-Key
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Connect
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
x-refined-from:
- creator-api-com-openapi.json
- creator-api-com-openapi.json