> ## 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 person email
> Returns a contactable email for a person, found via a waterfall across multiple data providers. Use the optional type parameter to request a professional or personal email. If you omit it, the endpoint returns a professional email where available, otherwise a personal one. Each response states which type it returned.
Costs 1 credit per email returned.
## What you need
A Specter person ID (`per_…`); get one from [Search person name](/api-reference/people/search-person-name) or [Enrich person by email](/api-reference/enrich/enrich-person-by-email).
## Behaviour
- Returns a single email with its `type` (`professional` or `personal`).
- Returns `204` if the person exists but no email is available.
- Returns `404` if the person ID doesn't exist.
## What you do next
- **Open the full profile.** Get career history, skills, and education with [Get person by ID](/api-reference/people/get-person-by-id).
## OpenAPI
````yaml /api-ref/bundle_api.yaml get /people/{personId}/email
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:
/people/{personId}/email:
get:
tags:
- People
summary: Get person email
description: >
Returns a contactable email for a person, found via a waterfall across
multiple data providers. Use the optional type parameter to request a
professional or personal email. If you omit it, the endpoint returns a
professional email where available, otherwise a personal one. Each
response states which type it returned.
Costs 1 credit per email returned.
## What you need
A Specter person ID (`per_…`); get one from [Search person
name](/api-reference/people/search-person-name) or [Enrich person by
email](/api-reference/enrich/enrich-person-by-email).
## Behaviour
- Returns a single email with its `type` (`professional` or `personal`).
- Returns `204` if the person exists but no email is available.
- Returns `404` if the person ID doesn't exist.
## What you do next
- **Open the full profile.** Get career history, skills, and education
with [Get person by ID](/api-reference/people/get-person-by-id).
parameters:
- $ref: '#/components/parameters/PersonId'
- in: query
name: type
schema:
type: string
enum:
- professional
- personal
required: false
allowEmptyValue: true
description: |
Determine if only a specific kind of email should be returned.
responses:
'200':
description: The email address of the person if found
content:
application/json:
schema:
type: object
required:
- email
- type
properties:
email:
type: string
description: The person's email address.
example: jane.doe@example.com
type:
type: string
description: Which kind of email was returned.
enum:
- professional
- personal
example: personal
'204':
description: >
The person exists in our system but an email address was not
available
'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:
PersonId:
in: path
name: personId
schema:
type: string
required: true
description: The ID of the person being requested.
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
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
````