> ## 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 company employees
> Returns the people Specter has on file for a company (founders and employees) as a list. Use each `person_id` with [Get person by ID](/api-reference/people/get-person-by-id) to pull a full profile.
Costs 1 credit per request.
## What you need
A Specter `companyId` (via [Find company ID](/api-reference/companies/find-company-id) or [Search company name](/api-reference/companies/search-company-name)).
## Behaviour
- Returns at most 100 people per request (default 50).
- Narrow results with `founders`, `ceo`, `key_people`, and `department`; these filters can be combined.
- Page through large teams with `limit` and `page` (`page` is zero-based).
- Returns `404` if the company ID doesn't exist.
## What you do next
- **Profile a person.** Follow a person's `person_id` to [Get person by ID](/api-reference/people/get-person-by-id).
- **Get their email.** Pull a contactable address with [Get person email](/api-reference/people/get-person-email).
- **Watch their moves.** Follow a person's `talent_signal_ids` to [Get Talent Signal by ID](/api-reference/talent-signals/get-talent-signal-by-id).
## OpenAPI
````yaml /api-ref/bundle_api.yaml get /companies/{companyId}/people
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:
/companies/{companyId}/people:
get:
tags:
- Companies
summary: Get company employees
description: >
Returns the people Specter has on file for a company (founders and
employees) as a list. Use each `person_id` with [Get person by
ID](/api-reference/people/get-person-by-id) to pull a full profile.
Costs 1 credit per request.
## What you need
A Specter `companyId` (via [Find company
ID](/api-reference/companies/find-company-id) or [Search company
name](/api-reference/companies/search-company-name)).
## Behaviour
- Returns at most 100 people per request (default 50).
- Narrow results with `founders`, `ceo`, `key_people`, and `department`;
these filters can be combined.
- Page through large teams with `limit` and `page` (`page` is
zero-based).
- Returns `404` if the company ID doesn't exist.
## What you do next
- **Profile a person.** Follow a person's `person_id` to [Get person by
ID](/api-reference/people/get-person-by-id).
- **Get their email.** Pull a contactable address with [Get person
email](/api-reference/people/get-person-email).
- **Watch their moves.** Follow a person's `talent_signal_ids` to [Get
Talent Signal by
ID](/api-reference/talent-signals/get-talent-signal-by-id).
parameters:
- $ref: '#/components/parameters/CompanyId'
- $ref: '#/components/parameters/PaginationLimit'
- $ref: '#/components/parameters/PaginationPage'
- in: query
name: founders
schema:
type: boolean
required: false
allowEmptyValue: true
description: Return only founders.
- in: query
name: ceo
schema:
type: boolean
required: false
allowEmptyValue: true
description: Return only CEOs (a company can have more than one).
- in: query
name: key_people
schema:
type: boolean
required: false
allowEmptyValue: true
description: >-
Return only key people (CEO, CTO, CFO, COO, and current or past
founders).
- in: query
name: department
schema:
type: string
enum:
- BD & Marketing
- Engineering
- Finance
- Human Resources
- Legal & Compliance
- Operations
- Product & Research
- Senior Leadership
- Strategy & Corporate Development
- Other
required: false
allowEmptyValue: true
description: Return only people in the given department.
responses:
'200':
$ref: '#/components/responses/TeamBreakdownResponse'
'400':
description: 'Bad request: invalid query parameters.'
content:
application/json:
schema:
type: object
properties:
errorCode:
type: string
example: VALIDATION_ERROR
message:
type: string
example: Invalid request parameters.
'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:
CompanyId:
in: path
name: companyId
schema:
type: string
required: true
description: The Specter company ID.
PaginationLimit:
in: query
name: limit
schema:
type: number
required: false
description: The number of results to return, default is 50.
PaginationPage:
in: query
name: page
schema:
type: number
required: false
description: The page number of results to return, base 0, default is 0.
responses:
TeamBreakdownResponse:
description: The people who work at the company.
content:
application/json:
schema:
type: array
items:
type: object
properties:
person_id:
type: string
nullable: true
example: per_34f8a8ad1f7497b83e821345
description: >-
The person's Specter ID, usable on the people endpoints (may
be null for legacy records).
full_name:
type: string
example: Cosmin Urdea
description: The person's full name.
title:
type: string
nullable: true
example: (valantic mandate / partnership) Stripe Integration Engineer
description: The person's job title (may be null).
is_founder:
type: boolean
example: false
description: Whether the person is a founder.
departments:
type: array
items:
type: string
enum:
- BD & Marketing
- Engineering
- Finance
- Human Resources
- Legal & Compliance
- Operations
- Product & Research
- Senior Leadership
- Strategy & Corporate Development
- Other
example:
- Engineering
description: The departments the person belongs to (may be empty).
example:
- Engineering
seniority:
type: string
nullable: true
example: Mid Level
description: The person's seniority level (may be null).
required:
- full_name
- is_founder
- person_id
- title
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
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
````