> ## 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 saved search details
>
**What it does**
Returns summary details for a saved people search—including its name, query_id, and the number of people matched.
**Why you’d use it**
Quickly gauge the size and relevance of a saved people search before deciding to fetch full results.
**Key behaviors**
- Provides metadata only (no per-person records). Use the GET saved people search
results endpoint to retrieve individuals.
The saved search must be shared to the API via "Share to API", or be a global search curated by Specter, to be queried. Searches shared only within your team or organization are not accessible from the API.
## OpenAPI
````yaml /api-ref/bundle_api.yaml get /searches/people/{searchId}
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:
/searches/people/{searchId}:
get:
tags:
- People Saved Searches
summary: Get people saved search details
description: >
**What it does**
Returns summary details for a saved people search—including its name,
query_id, and the number of people matched.
**Why you’d use it**
Quickly gauge the size and relevance of a saved people search before
deciding to fetch full results.
**Key behaviors**
- Provides metadata only (no per-person records). Use the GET saved
people search
results endpoint to retrieve individuals.
The saved search must be shared to the API via "Share to API", or be a
global search curated by Specter, to be queried. Searches shared only
within your team or organization are not accessible from the API.
operationId: getPeopleSearch
parameters:
- $ref: '#/components/parameters/SearchId'
responses:
'200':
$ref: '#/components/responses/BasicSearchIdResponse'
'400':
description: BadRequest
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/SearchIdBadRequest'
- $ref: '#/components/schemas/NotSupportedProduct'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'429':
$ref: '#/components/responses/RateLimits'
components:
parameters:
SearchId:
in: path
name: searchId
schema:
type: string
required: true
description: The ID of the saved search being requested.
responses:
BasicSearchIdResponse:
description: The details of the query for a given search id.
content:
application/json:
schema:
type: object
properties:
id:
description: >
The search id for the search, this should be used to query for
results for the search.
type: number
example: 163
name:
description: Name of the search
type: string
example: European Query
is_global:
description: This flags searches recommended by Specter for all users
type: boolean
example: false
query_id:
description: >
The query id that this search is related to, this can be used
to query for the search in the address bar.
`https://app.staging.tryspecter.com/signals/{product_type}/feed?queryId=10`
type: number
example: 10
product_type:
description: The type of product the search relates to.
type: string
enum:
- company
- investors
- people
- talent
full_count:
description: |
The total number of items that are returned by this search.
type: number
example: 100
Unauthorized:
description: Unauthorized
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/ApiKeyMissing'
- $ref: '#/components/schemas/ApiKeyNotValid'
Forbidden:
description: Forbidden - There is no permissions to use the endpoint
content:
application/json:
schema:
type: object
properties:
errorCode:
description: NOT_PERMITTED
type: string
example: NOT_PERMITTED
message:
type: string
description: You do not have permission to access this resource.
example: You do not have permission to access this resource.
required:
- errorCode
- message
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:
SearchIdBadRequest:
properties:
errorCode:
type: string
description: BAD_SEARCH_ID_TYPE
example: BAD_SEARCH_ID_TYPE
message:
type: string
description: The search id needs to be a number.
example: The search id needs to be a number.
NotSupportedProduct:
properties:
errorCode:
type: string
description: NOT_SUPPORTED_PRODUCT
example: NOT_SUPPORTED_PRODUCT
message:
type: string
description: >
Details the product that was requested and the product that is
supported.
example: >
The product "people" is not support by this operation. Only
"companies" are supported.
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
````