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

# List accounts

> Companies Openpulse has found signals about, cursor-paginated. One row per company rather than per post, which is usually the shape a sales question wants.

Requires a plan that includes account intelligence; a workspace without it gets a 403 naming the plan rather than an empty list.



## OpenAPI

````yaml /api-reference/openapi.json get /v1/accounts
openapi: 3.1.0
info:
  title: Openpulse API
  version: 1.0.0
  summary: Read buying signals, accounts and pipeline from an Openpulse workspace.
  description: >-
    The programmatic surface of Openpulse, authenticated with a workspace API
    key.


    **A key always acts as a member, never an admin.** Privilege comes from
    scopes, and

    the scope vocabulary has no way to express an admin action: a leaked key can
    read

    signals and move deals, and can never create a listener, change billing, or
    mint

    another key. Routes that declare no scope are unreachable by a key at all,
    which is

    why this document describes fewer operations than the server has handlers.


    For an assistant rather than a program, prefer the MCP server at `/mcp`: it
    is the

    same data with tool descriptions a model can act on, and it uses OAuth
    rather than a

    shared secret. See `/api.md`.


    **Webhooks**, described below, are the other direction: calls this
    workspace's server

    makes to yours. Verify each one by recomputing the HMAC and comparing it to
    the

    `x-openpulse-signature` header — an unverified delivery is a POST from
    anyone

    who finds the URL, not proof it came from Openpulse.
  contact:
    email: support@openpulse.cloud
    url: https://openpulse.cloud/api.md
  license:
    name: Proprietary
    identifier: LicenseRef-Openpulse-Terms
servers:
  - url: https://api.openpulse.cloud
    description: Production
security:
  - apiKey: []
externalDocs:
  url: https://openpulse.cloud/api.md
  description: Openpulse for agents
paths:
  /v1/accounts:
    get:
      tags:
        - accounts
      summary: List accounts
      description: >-
        Companies Openpulse has found signals about, cursor-paginated. One row
        per company rather than per post, which is usually the shape a sales
        question wants.


        Requires a plan that includes account intelligence; a workspace without
        it gets a 403 naming the plan rather than an empty list.
      operationId: getV1Accounts
      parameters:
        - name: limit
          in: query
          description: Page size, 1-100.
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 25
        - name: cursor
          in: query
          description: '`nextCursor` from the previous page.'
          schema:
            type: string
        - name: owner
          in: query
          description: Only accounts assigned to this member.
          schema:
            type: string
        - name: region
          in: query
          description: Only accounts in this region.
          schema:
            type: string
      responses:
        '200':
          description: Success.
          content:
            application/json:
              schema:
                type: object
        '401':
          description: The key is missing, malformed, expired or revoked.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            The key lacks the `accounts:read` scope, or the workspace's plan
            does not include this.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: Rate limited. Retry after the interval in the response headers.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - apiKey:
            - accounts:read
components:
  schemas:
    Error:
      type: object
      properties:
        message:
          type: string
          description: Human-readable explanation.
        code:
          type: string
          description: Stable machine-readable error code.
      required:
        - message
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: >-
        A workspace API key, created in workspace settings and sent as
        `Authorization: Bearer op_live_…`. Session cookies are not accepted.
        Scopes: signals:read, accounts:read, listeners:read, listeners:analyse,
        pipeline:read, pipeline:write, collections:write, export:read.

````

## Related topics

- [Accounts and territory](/guides/accounts-and-territory.md)
- [Get one account](/api-reference/accounts/get-one-account.md)
- [Runs and signals](/guides/runs-and-signals.md)