> ## 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 investor by ID
> Returns the full Specter investor record for a single investor ID — profile, activity, targeting, funds, and portfolio companies. Resolve any `portfolio_companies` ID with [Get company by ID](/api-reference/companies/get-company-by-id).
Costs 1 credit per request.
## Behaviour
- `person_id` is set when the investor is an individual (e.g. an angel); `company_id` is set when there's an associated company (e.g. the firm behind a fund). Either, both, or neither may be `null`.
- Returns `404` if the investor ID doesn't exist.
## OpenAPI
````yaml /api-ref/bundle_api.yaml get /investors/{investorId}
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:
/investors/{investorId}:
get:
tags:
- Investors
summary: Get investor by ID
description: >
Returns the full Specter investor record for a single investor ID —
profile, activity, targeting, funds, and portfolio companies. Resolve
any `portfolio_companies` ID with [Get company by
ID](/api-reference/companies/get-company-by-id).
Costs 1 credit per request.
## Behaviour
- `person_id` is set when the investor is an individual (e.g. an angel);
`company_id` is set when there's an associated company (e.g. the firm
behind a fund). Either, both, or neither may be `null`.
- Returns `404` if the investor ID doesn't exist.
parameters:
- $ref: '#/components/parameters/InvestorId'
responses:
'200':
description: The investor.
content:
application/json:
schema:
$ref: '#/components/schemas/Investor'
'401':
$ref: '#/components/responses/Unauthorized'
'402':
$ref: '#/components/responses/OutOfCredits'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'429':
$ref: '#/components/responses/RateLimits'
components:
parameters:
InvestorId:
in: path
name: investorId
schema:
type: string
required: true
description: >-
The ID of the investor being requested (e.g.
`inv_5f3a2b1c4d5e6f7a8b9c0d1e`).
schemas:
Investor:
title: Investor
type: object
required:
- investor_id
- investor_name
- strategic_signal_ids
- investor_types
- investment_stage
- industry_target
- specter_industry_target
- specter_tech_verticals_target
- fund_details
- portfolio_companies
additionalProperties: false
properties:
investor_id:
type: string
description: The Specter ID for this investor, can be used in other endpoints.
example: inv_609dba55408c4490fe58cf8e
strategic_signal_ids:
type: array
description: >-
All Interest Signals IDs associated with this investor. Empty when
none are active.
items:
type: string
format: uuid
example: ddea4a84-ffdc-459d-bb10-3d7db9c6c193
person_id:
type: string
nullable: true
description: >-
The Specter person ID this investor is linked to, when the investor
is an individual (e.g. an angel). `null` for firms.
example: 5e3b9281137e998b5aea67f4
company_id:
type: string
nullable: true
description: >-
The Specter company ID of the company associated with this investor,
when applicable (e.g. the firm behind a VC fund).
example: 5e3b9281137e998b5aea67f4
investor_name:
type: string
description: The legal or brand name of the investor or investment firm.
example: Bessemer Venture Partners
investor_rank:
type: integer
nullable: true
description: The Specter rank for this investor.
example: 43
company_size:
type: string
nullable: true
description: >-
The size bracket of the investor's organization (employee count
band).
example: 201-500
operating_status:
type: string
nullable: true
description: The operating status of the investor (e.g. `active`, `closed`).
example: active
domain:
type: string
nullable: true
description: The investor's primary web domain.
example: bvp.com
hq_location:
type: string
nullable: true
description: The investor's headquarters location.
example: San Francisco, California, United States, North America
founded_year:
type: integer
nullable: true
description: The year the investor was founded.
example: 1911
investor_types:
type: array
description: >-
The investor types this investor falls under, as lowercase
snake_case (e.g. `venture_capital`, `angel_group`).
items:
type: string
example: venture_capital
linkedin_url:
type: string
nullable: true
description: The investor's LinkedIn profile URL.
example: linkedin.com/company/bessemer-venture-partners
twitter_url:
type: string
nullable: true
description: The investor's Twitter / X profile URL.
example: x.com/BessemerVP
description:
type: string
nullable: true
description: >-
Brief textual overview of the investor’s activities, history, or
focus.
example: >-
Bessemer Venture Partners is a leading venture capital firm that
partners with entrepreneurs from their early days through every
stage of growth.
number_of_exits:
type: integer
nullable: true
description: Total number of portfolio company exits attributed to this investor.
example: 325
number_of_lead_investments:
type: integer
nullable: true
description: Total number of investments where the investor led the round.
example: 574
number_of_investments:
type: integer
nullable: true
description: Total number of investments made by the investor.
example: 1581
number_of_funds:
type: integer
nullable: true
description: Total number of separate funds managed or raised by the firm.
example: 15
investment_stage:
type: array
description: >-
Typical funding round stages in which the investor participates
(e.g., Seed, Series A).
items:
type: string
example: Series A
industry_target:
type: array
description: Industries or verticals in which the investor typically specializes.
items:
type: string
example: Software
specter_industry_target:
type: array
description: >-
Only top level. Classifies companies by their economic activity —
the market they serve and the products or services they deliver.
E.g. Construction, Utilities, Wholesale. There is one industry per
company, with up to three levels.
items:
type: string
example: Enterprise Software
specter_tech_verticals_target:
type: array
description: >-
Only top level. Classifies companies by the technology domain they
operate in — the technical capability or space they're building
around. E.g. AI & Machine Learning, Cybersecurity, FinTech. There
can be up to 5 tech verticals per company, with 2 levels each.
items:
type: string
example: AI / Machine Learning
fund_details:
type: array
description: >-
The named funds this investor has raised, with announce date and
amount when available.
items:
$ref: '#/components/schemas/InvestorFund'
portfolio_companies:
type: array
description: Specter company IDs for portfolio companies of this investor.
items:
type: string
example: 5e3bbf6b00c8f4c966a1e53d
InvestorFund:
title: InvestorFund
type: object
description: A single fund raised by an investor.
additionalProperties: false
properties:
name:
type: string
nullable: true
description: The fund's name.
example: BVP Fund XII
announced_on:
type: string
format: date
nullable: true
description: ISO date (YYYY-MM-DD) the fund was announced.
example: '2023-04-12'
raised_amount_usd:
type: string
nullable: true
description: Amount raised in USD.
example: '3850000000'
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
responses:
Unauthorized:
description: Unauthorized
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/ApiKeyMissing'
- $ref: '#/components/schemas/ApiKeyNotValid'
OutOfCredits:
description: Out of credits - API credit limit exceeded
content:
application/json:
schema:
type: object
required:
- errorCode
- message
properties:
errorCode:
type: string
enum:
- OUT_OF_CREDITS
message:
type: string
description: |
There are no more credits available to complete the request.
headers:
X-CreditLimit-Limit:
schema:
type: integer
description: The total number of credits allocated for the current period
X-CreditLimit-Remaining:
schema:
type: integer
description: The number of credits remaining for the current period
X-CreditLimit-Reset:
schema:
type: number
format: float
description: The number of seconds until the credit limit resets
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
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: X-API-Key
````