> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List LinkedIn accounts

> **Read-only.** It changes nothing.

The LinkedIn accounts connected to this account. A campaign sends from exactly one of them, attached via `campaign_update`; if there is more than one, ask the user which. Whether an account has a Sales Navigator or Recruiter seat is NOT in this output — those flags exist on the account record but are not exposed by the API, and the worker only sets them during a send. Ask the user, because INMAILS steps and `/sales/` or `/talent/` lead sources depend on it. Check `isValid`, `isPaused`, `accountRestricted` and `weeklyLimitReached` before assigning an account — a campaign attached to a broken account will launch but never send. This lists; it does not connect. Adding a LinkedIn account takes a password and a verification PIN and has no endpoint at all — it is done in the web app. Attaching an existing account to a campaign is `campaign_update`, and changing the account's own limits is `linkedin_account_update`.



## OpenAPI

````yaml /api-v2/openapi.json post /linkedin_account_list
openapi: 3.1.0
info:
  title: LinkedCamp API
  version: 2.0.0
  description: >-
    Version 2 of the LinkedCamp API. Every endpoint is a POST to `/{endpoint}`
    with its arguments as a JSON object, and returns JSON.
servers:
  - url: https://api.linkedcamp.com/v2
security:
  - ApiKey: []
  - Bearer: []
tags:
  - name: Account
  - name: Notifications
  - name: Reference
  - name: Campaigns
  - name: Campaign audience
  - name: Sequences
  - name: Blocked dates
  - name: Leads
  - name: Lead notes
  - name: Activities
  - name: Tags
  - name: Blacklist
  - name: Conversations
  - name: Messages
  - name: Saved replies
  - name: Templates
  - name: Merge fields
  - name: Personalised images
  - name: LinkedIn accounts
  - name: Email accounts
  - name: AI agents
  - name: Knowledge base
  - name: Personas
  - name: Analytics
  - name: Posts
  - name: Posting schedule
  - name: Tasks
  - name: Appointments
  - name: Reminders
  - name: Automations
paths:
  /linkedin_account_list:
    post:
      tags:
        - LinkedIn accounts
      summary: List LinkedIn accounts
      description: >-
        **Read-only.** It changes nothing.


        The LinkedIn accounts connected to this account. A campaign sends from
        exactly one of them, attached via `campaign_update`; if there is more
        than one, ask the user which. Whether an account has a Sales Navigator
        or Recruiter seat is NOT in this output — those flags exist on the
        account record but are not exposed by the API, and the worker only sets
        them during a send. Ask the user, because INMAILS steps and `/sales/` or
        `/talent/` lead sources depend on it. Check `isValid`, `isPaused`,
        `accountRestricted` and `weeklyLimitReached` before assigning an account
        — a campaign attached to a broken account will launch but never send.
        This lists; it does not connect. Adding a LinkedIn account takes a
        password and a verification PIN and has no endpoint at all — it is done
        in the web app. Attaching an existing account to a campaign is
        `campaign_update`, and changing the account's own limits is
        `linkedin_account_update`.
      operationId: linkedin_account_list
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                keyword:
                  type: string
                  description: Filter by name or email.
                status:
                  type: string
                  description: >-
                    Backend-side status filter, e.g. "active", "paused",
                    "invalid".
                userId:
                  type: string
                  description: >-
                    Read a SUB-ACCOUNT instead of your own data. Accepted only
                    from an agency owner, and only for an account inside your
                    own agency: take the id from `subaccount_list` and never
                    construct or guess one. An id outside that list is refused.
                    Omit it to read your own data, and name the account to the
                    user when you pass it.
              additionalProperties: false
      responses:
        '200':
          description: >-
            The result, as JSON. Writes answer `{ "ok": true, "message": ...,
            "data": ... }`.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: >-
            The body is not valid JSON, an argument is invalid, or the request
            was refused.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: No API key, or the key was rejected.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            Your plan, permissions or access tier don't include this, or a
            record belongs to another account.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: A record named in the arguments does not exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '422':
          description: >-
            The request was valid but the operation was refused, such as
            launching a campaign that is not ready.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '502':
          description: The service failed or could not be reached. Reads are safe to retry.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '504':
          description: >-
            The operation timed out. A write may still complete; read it back
            before retrying.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              enum:
                - UNAUTHENTICATED
                - FORBIDDEN
                - PLAN_REQUIRED
                - VALIDATION
                - INVALID_JSON
                - NOT_FOUND
                - METHOD_NOT_ALLOWED
                - UPSTREAM
                - TOOL_ERROR
            message:
              type: string
            hint:
              type: string
              description: What to do about it, when there is something to do.
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: X-Api-Key
      description: Your LinkedCamp API key.
    Bearer:
      type: http
      scheme: bearer
      description: Your LinkedCamp API key as a bearer token.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.