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

# Get specific investor list info

> Retrieve detailed information about a specific investor list reachable from your API key: created via the API, with "Share to API" turned on, or a global list curated by Specter. Includes the ids of the investors it contains. Lists shared only within your team are not accessible from the API.




## OpenAPI

````yaml /api-ref/bundle_api.yaml get /lists/investors/{listId}
openapi: 3.0.0
info:
  title: Specter API
  termsOfService: https://tryspecter.com/terms/
  contact:
    name: API support
    email: api-support@tryspecter.com
  version: 1.0.0
servers:
  - description: Production
    url: https://app.tryspecter.com/api/v1
security:
  - ApiKeyAuth: []
tags:
  - name: Enrichment
    description: >
      Endpoints which can be used to query for data and, if the data is not
      found request that it be retrieved by Specter systems.
  - name: Companies
    description: >
      Endpoints that provide the most up to date information about all the
      companies in our data set. Giving the ability to query by a specific
      company id, or using a keyword such as the domain.


      This also allows us to enrich the data about a company if we either do not
      have it or it is older than expected, which means you always have the most
      up-to-date information possible.
  - name: People
    description: >
      Endpoints that expose Specter people records — profile data and contact
      details — for a known person ID.
  - name: Investors
    description: >
      Endpoints that expose Specter investor records — profile, activity,
      targeting, funds, portfolio companies, and the funding rounds they have
      participated in — for a known investor ID.
  - name: Talent and Interest Signals
    description: >
      Endpoints for retrieving Specter Talent Signals and Investor Interest
      Signals by ID.
  - name: News Signals
    description: >
      Company-level news signals generated from articles monitored by Specter.
      Each signal represents a single classified company mention within an
      article and includes a summary of the newsworthy update (such as funding,
      deals, revenue, profitability, or traction) along with an assigned
      importance score.
  - name: Revenue Signals
    description: >
      Revenue and profitability observations for companies, derived from news
      coverage and public filings. Each signal captures one data point — the
      revenue or profitability metric, the year it refers to, the source, and
      the company it is attributed to.
  - name: Transactions
    description: >
      Endpoints that expose transaction detail — funding rounds, acquisitions,
      and IPOs — by ID.
  - name: Company Lists
    description: >
      Create, query and maintain lists of companies that are of particular
      interest. The endpoints here allow you to interrogate and maintain those
      lists using a programmatic interface.
  - name: People Lists
    description: >
      Create, query and maintain lists of people that are of particular
      interest. The endpoints here allow you to interrogate and maintain those
      lists using a programmatic interface.
  - name: Investor Lists
    description: >
      Create, query and maintain lists of investors that are of particular
      interest. The endpoints here allow you to interrogate and maintain those
      lists using a programmatic interface.
  - name: Network
    description: >
      Endpoints for accessing your team's LinkedIn network - the people and
      companies your teammates are connected to.
  - name: Saved Searches
    description: >
      Manage searches that have been saved via `tryspecter.com`. These endpoints
      are useful to programmatically list and delete saved searches. To update a
      search the UI should be used at `tryspecter.com`.
  - name: Company Saved Searches
    description: >
      Query and get results for company searches that have been saved via
      `tryspecter.com`. These endpoints are useful to programmatically get
      results and information for a search. To update a search the UI should be
      used at `tryspecter.com`.
  - name: People Saved Searches
    description: >
      Query and get results for people searches that have been saved via
      `tryspecter.com` or via the API. These endpoints are useful to
      programmatically get results and information for a search. To update a
      search the UI should be used at `tryspecter.com`.
  - name: Investor Saved Searches
    description: >
      Query and inspect saved investor searches — metadata (name, match counts)
      and paginated results — from searches saved via `tryspecter.com` or shared
      with the API.
  - name: Talent Signals Saved Searches
    description: >
      Query and get results for Talent Signals searches that have been saved via
      `tryspecter.com`.
  - name: Investor Interest Saved Searches
    description: >
      Query and get results for Investor Interest Signals searches that have
      been saved via `tryspecter.com`.
  - name: Organization
    description: >
      Endpoints for accessing your organization's members and org-level
      resources.
  - name: Customer Data
    description: >
      Retrieve a log of API calls made by your organization. Useful for auditing
      usage, debugging integrations, and monitoring activity.
paths:
  /lists/investors/{listId}:
    get:
      tags:
        - Investor Lists
      summary: Get specific investor list info
      description: >
        Retrieve detailed information about a specific investor list reachable
        from your API key: created via the API, with "Share to API" turned on,
        or a global list curated by Specter. Includes the ids of the investors
        it contains. Lists shared only within your team are not accessible from
        the API.
      operationId: getInvestorList
      parameters:
        - $ref: '#/components/parameters/ListId'
      responses:
        '200':
          $ref: '#/components/responses/InvestorListResponse'
        '400':
          $ref: '#/components/responses/ListUUIDBadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '429':
          $ref: '#/components/responses/RateLimits'
components:
  parameters:
    ListId:
      in: path
      name: listId
      schema:
        type: string
        format: uuid
      required: true
      description: The ID of the list being requested.
  responses:
    InvestorListResponse:
      description: The list including investor ids
      content:
        application/json:
          schema:
            type: object
            properties:
              id:
                description: List Id
                type: string
                format: uuid
                example: b73c8bed-3b92-48f9-a879-40ee114dca03
              name:
                description: Name of the list
                type: string
                example: Top European Seed VCs
              created_at:
                description: Date (YYYY:MM:DD) the list was created.
                type: string
                format: date-time
                example: '2024-11-14T10:36:12.625Z'
              updated_at:
                description: Date (YYYY:MM:DD) the list was last updated.
                type: string
                format: date-time
                example: '2024-11-14T10:36:12.625Z'
              investors:
                description: The investors included in this list
                type: array
                items:
                  type: object
                  properties:
                    investor_id:
                      description: The Specter ID of the investor
                      type: string
                      example: inv_5e3a7f2b0aa7a3270a55f2a7
                    created_at:
                      description: Date (YYYY:MM:DD) the investor was added to the list.
                      type: string
                      format: date-time
                      example: '2025-01-02T17:29:46.688Z'
    ListUUIDBadRequest:
      description: Bad Request
      content:
        application/json:
          schema:
            type: object
            properties:
              errorCode:
                type: string
                description: The type of error.
              message:
                type: string
                description: >
                  A message with information about why the request was bad, will
                  be either a single message, or a path to the validation
                  issues.
          examples:
            list-id-not-uuid:
              summary: Invalid List UUID
              value:
                errorCode: INVALID_LIST_UUID
                message: List id must be a valid UUID.
    Unauthorized:
      description: Unauthorized
      content:
        application/json:
          schema:
            oneOf:
              - $ref: '#/components/schemas/ApiKeyMissing'
              - $ref: '#/components/schemas/ApiKeyNotValid'
    NotFound:
      description: Not Found
      content:
        application/json:
          schema:
            type: object
            required:
              - errorCode
              - message
            properties:
              errorCode:
                type: string
                description: NOT_FOUND
              message:
                type: string
                description: Not Found
    RateLimits:
      description: Too Many Requests - API Rate limit exceeded
      content:
        application/json:
          schema:
            type: object
            required:
              - errorCode
              - message
            properties:
              errorCode:
                type: string
                description: RATE_LIMITED
              message:
                type: string
                description: You have been rate-limited
      headers:
        X-RateLimit-Limit:
          schema:
            type: integer
          description: The total rate limit allowed for this endpoint
        X-RateLimit-Remaining:
          schema:
            type: integer
          description: The number of requests remaining
        X-RateLimit-Reset:
          schema:
            type: number
            format: float
          description: The number of seconds until the rate limit resets
  schemas:
    ApiKeyMissing:
      properties:
        errorCode:
          description: API_KEY_MISSING
          example: API_KEY_MISSING
          type: string
        message:
          description: No API Key was presented on the header X-API-KEY
          example: No API Key was presented on the header X-API-KEY
          type: string
    ApiKeyNotValid:
      properties:
        errorCode:
          description: API_KEY_NOT_VALID
          example: API_KEY_NOT_VALID
          type: string
        message:
          description: API key present, but not valid
          example: API key present, but not valid
          type: string
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key

````