> ## 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 agency sub-accounts

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

The active sub-accounts under your agency: id, name, email, plan and state. Owner-only — the backend refuses it for any other role. This is where a `userId` comes from. The seven endpoints that accept one — `campaign_list`, `linkedin_account_list`, `email_account_list`, `analytics_campaign`, `analytics_reporting`, `tag_list`, `agent_duplicate` — read that sub-account's data instead of yours, and an id from outside this list is refused. Never guess or construct a `userId`; take it from here, and tell the user whose account you are about to read. Only active sub-accounts holding a plan are returned: disabled, deleted and plan-less accounts are filtered out here rather than upstream, and `excluded` says how many were dropped. An account that is not listed cannot be passed as `userId` either. Distinct from `team_members_list`, which lists MANAGERs on your own account rather than separate accounts. Creating, disabling and licensing sub-accounts happens in the web app.



## OpenAPI

````yaml /api-v2/openapi.json post /subaccount_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:
  /subaccount_list:
    post:
      tags:
        - Account
      summary: List agency sub-accounts
      description: >-
        **Read-only.** It changes nothing.


        The active sub-accounts under your agency: id, name, email, plan and
        state. Owner-only — the backend refuses it for any other role. This is
        where a `userId` comes from. The seven endpoints that accept one —
        `campaign_list`, `linkedin_account_list`, `email_account_list`,
        `analytics_campaign`, `analytics_reporting`, `tag_list`,
        `agent_duplicate` — read that sub-account's data instead of yours, and
        an id from outside this list is refused. Never guess or construct a
        `userId`; take it from here, and tell the user whose account you are
        about to read. Only active sub-accounts holding a plan are returned:
        disabled, deleted and plan-less accounts are filtered out here rather
        than upstream, and `excluded` says how many were dropped. An account
        that is not listed cannot be passed as `userId` either. Distinct from
        `team_members_list`, which lists MANAGERs on your own account rather
        than separate accounts. Creating, disabling and licensing sub-accounts
        happens in the web app.
      operationId: subaccount_list
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                keyword:
                  type: string
                  description: Filter by name.
                page:
                  type: integer
                  minimum: 1
                  default: 1
                  description: 1-indexed page number.
                pageSize:
                  type: integer
                  minimum: 1
                  maximum: 200
                  default: 50
                  description: Rows per page.
              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.