> ## 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 people list
> Returns information about a people list created or shared with the API, including the people it contains.
Free. This call does not consume credits.
## What you need
A list ID (UUID); get one from [Get all people lists](/api-reference/people-lists/get-all-people-lists).
## Behaviour
- `listId` must be a UUID, otherwise `400`.
- Returns `404` if the list doesn't exist or isn't visible to the API.
## What you do next
- **Get full people data.** Pull profiles via [Get people list results](/api-reference/people-lists/get-people-list-results).
- **Open a single person.** Pass a `person_id` to [Get person by ID](/api-reference/people/get-person-by-id).
## OpenAPI
````yaml /api-ref/bundle_api.yaml get /lists/people/{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: Enrich
description: >
Look up a company, person, or investor and, if Specter does not already
hold it, fetch it on demand. Includes email-based person enrichment.
- name: Search
description: |
Find records across every product from a single plain-English query.
- name: Companies
description: >
Company profiles, funding, headcount, traction, the per-company signals
and sub-resources attached to a single company, and identifier resolution.
- name: People
description: >
Specter people records: profile data, contact details, and per-person
lookups for a known person ID.
- name: Investors
description: >
Specter investor records: profile, activity, targeting, funds, portfolio
companies, and the funding rounds they have participated in.
- name: Transactions
description: |
Transaction detail by ID: funding rounds, acquisitions, and IPOs.
- name: News Signals
description: |
Company-level news signals: by ID, and for a saved list or company search.
- name: Revenue Signals
description: >
Revenue and profitability signals: by ID, by date, and for a saved list or
company search.
- name: Talent Signals
description: |
Talent signals: by ID and in bulk by ID.
- name: Investor Interest Signals
description: |
Investor interest signals: by ID and in bulk by ID.
- name: Company Lists
description: |
Create, query, and maintain lists of companies, including their results.
- name: Investor Lists
description: |
Create, query, and maintain lists of investors, including their results.
- name: People Lists
description: |
Create, query, and maintain lists of people, including their results.
- name: Saved Searches
description: |
List and delete searches saved via tryspecter.com.
- name: Company Saved Searches
description: |
Details and results for saved company searches.
- name: People Saved Searches
description: |
Details and results for saved people searches.
- name: Investor Saved Searches
description: |
Details and results for saved investor searches.
- name: Talent Signals Saved Searches
description: |
Details and results for saved Talent Signals searches.
- name: Investor Interest Saved Searches
description: |
Details and results for saved Investor Interest Signals searches.
- name: Network
description: >
Your team's LinkedIn network: the people and companies your teammates are
connected to, and your reach into a given company.
- name: Account
description: >
Organisation-level resources: your team's members, API call logs, and
credit balance.
paths:
/lists/people/{listId}:
get:
tags:
- People Lists
summary: Get people list
description: >
Returns information about a people list created or shared with the API,
including the people it contains.
Free. This call does not consume credits.
## What you need
A list ID (UUID); get one from [Get all people
lists](/api-reference/people-lists/get-all-people-lists).
## Behaviour
- `listId` must be a UUID, otherwise `400`.
- Returns `404` if the list doesn't exist or isn't visible to the API.
## What you do next
- **Get full people data.** Pull profiles via [Get people list
results](/api-reference/people-lists/get-people-list-results).
- **Open a single person.** Pass a `person_id` to [Get person by
ID](/api-reference/people/get-person-by-id).
operationId: getPeopleList
parameters:
- $ref: '#/components/parameters/ListId'
responses:
'200':
$ref: '#/components/responses/PeopleListResponse'
'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:
PeopleListResponse:
description: The list including people ids
content:
application/json:
schema:
type: object
properties:
id:
description: List Id
type: string
example: dbc97c77-8928-434b-9d62-1b596719ec23
name:
description: Name of the list
type: string
example: My Watchlist
created_at:
description: Date list was created
type: string
format: date-time
example: '2026-07-17T16:22:17.608512Z'
updated_at:
description: Date the list was last updated
type: string
format: date-time
example: '2026-07-17T16:22:17.608512Z'
people:
description: The people included in this list
type: array
items:
properties:
person_id:
description: The Specter ID of the person
type: string
example: per_2f3c7fe468ec9fc2181bec8b
created_at:
description: The date the person was added to the list
type: string
format: date-time
example: '2026-07-17T16:22:17.608512Z'
required:
- id
- name
- people
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
````