> ## 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.
# Find person ID
> Resolve a batch of LinkedIn identifiers (profile URL, vanity id, numeric id, or URN) into the Specter `person_id`. Re-use that id with the id-only people endpoints such as [Get person by ID](/api-reference/people/get-person-by-id).
Free. This call does not consume credits. The id-only endpoints you call next are charged as usual.
## What you need
One or more LinkedIn identifiers to resolve (1–50 per request). No Specter ID is required; that is what this returns.
## Behaviour
- Pass identifiers under `to_resolve` (1–50 per request). Each entry must carry exactly one identifier; none, or more than one, returns a validation error.
- The response has one result group per input, in the same order, so you can attribute each result back to what you sent. `query` echoes the identifier.
- Every identifier form addresses a single profile, so `matches` holds at most one person.
- An identifier Specter doesn't hold keeps its place with an empty `matches` list. Nothing is enriched — use [Enrich person](/api-reference/enrich/enrich-person) when you want the profile fetched.
## What you do next
- **Get the full profile.** Pass the returned `person_id` to [Get person by ID](/api-reference/people/get-person-by-id).
- **Reach out.** Get a verified address with [Get person email](/api-reference/people/get-person-email).
- **Watch for moves.** Pull their signal history with [Get person talent signals](/api-reference/people/get-person-talent-signals).
## OpenAPI
````yaml /api-ref/bundle_api.yaml post /people/resolve
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: 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: Funding Rounds Saved Searches
description: |
Details and results for saved funding-round searches.
- name: Acquisitions Saved Searches
description: |
Details and results for saved acquisition searches.
- name: IPOs Saved Searches
description: |
Details and results for saved IPO 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/resolve:
post:
tags:
- People
summary: Find person ID
description: >
Resolve a batch of LinkedIn identifiers (profile URL, vanity id, numeric
id, or URN) into the Specter `person_id`. Re-use that id with the
id-only people endpoints such as [Get person by
ID](/api-reference/people/get-person-by-id).
Free. This call does not consume credits. The id-only endpoints
you call next are charged as usual.
## What you need
One or more LinkedIn identifiers to resolve (1–50 per request). No
Specter ID is required; that is what this returns.
## Behaviour
- Pass identifiers under `to_resolve` (1–50 per request). Each entry
must carry exactly one identifier; none, or more than one, returns a
validation error.
- The response has one result group per input, in the same order, so you
can attribute each result back to what you sent. `query` echoes the
identifier.
- Every identifier form addresses a single profile, so `matches` holds
at most one person.
- An identifier Specter doesn't hold keeps its place with an empty
`matches` list. Nothing is enriched — use [Enrich
person](/api-reference/enrich/enrich-person) when you want the profile
fetched.
## What you do next
- **Get the full profile.** Pass the returned `person_id` to [Get person
by ID](/api-reference/people/get-person-by-id).
- **Reach out.** Get a verified address with [Get person
email](/api-reference/people/get-person-email).
- **Watch for moves.** Pull their signal history with [Get person talent
signals](/api-reference/people/get-person-talent-signals).
requestBody:
description: The identifiers to resolve.
required: true
content:
application/json:
schema:
type: object
properties:
to_resolve:
type: array
minItems: 1
maxItems: 50
items:
$ref: '#/components/schemas/PersonResolveIdentifier'
required:
- to_resolve
additionalProperties: false
example:
to_resolve:
- linkedin_url: https://www.linkedin.com/in/patrickcollison
- linkedin_id: dhorowitz
- linkedin_num_id: 123456789
responses:
'200':
$ref: '#/components/responses/PersonResolveResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'422':
description: >
`to_resolve` is missing or empty, or an item provides no identifier,
more than one, or a malformed value (e.g. a LinkedIn URL that
carries no profile slug).
'429':
$ref: '#/components/responses/RateLimits'
components:
schemas:
PersonResolveIdentifier:
type: object
description: >
One LinkedIn identifier for a person. Supply exactly one of the fields
below; providing none, or more than one, returns a validation error. All
four address the same profile.
properties:
linkedin_url:
description: >
Person LinkedIn profile URL. Accepts `http`/`https`, with or without
`www`.
type: string
example: https://www.linkedin.com/in/patrickcollison
linkedin_id:
description: >
LinkedIn vanity id — the slug at the end of the profile URL, e.g.
`john-doe-123abc`.
type: string
example: patrickcollison
linkedin_num_id:
description: LinkedIn numeric member id.
type: integer
example: 123456789
linkedin_urn:
description: |
LinkedIn URN, a stable reference found in many datasets.
type: string
example: ACoAAAxxxxxxxx
additionalProperties: false
BasicPerson:
type: object
description: |
The minimum needed to identify a person and re-use their Specter id.
properties:
person_id:
description: Specter person id. Pass it to the id-only people endpoints.
type: string
example: per_7f8d9e2a1b3c4d5e6f7g8h9i0
full_name:
description: The person's full name.
type: string
example: Sarah Chen
linkedin_url:
description: The person's LinkedIn profile URL.
type: string
example: https://www.linkedin.com/in/sarahchen9776
required:
- person_id
additionalProperties: false
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:
PersonResolveResponse:
description: >
One result group per input identifier, in the same order as
`to_resolve`.
content:
application/json:
schema:
type: array
items:
type: object
properties:
query:
$ref: '#/components/schemas/PersonResolveIdentifier'
description: The identifier this group resolves.
matches:
description: >
The matching person, or an empty array when nothing matched.
At most one: every identifier form addresses a single
profile.
type: array
items:
$ref: '#/components/schemas/BasicPerson'
required:
- query
- matches
additionalProperties: false
example:
- query:
linkedin_url: https://www.linkedin.com/in/sarahchen9776
matches:
- person_id: per_7f8d9e2a1b3c4d5e6f7g8h9i0
full_name: Sarah Chen
linkedin_url: https://www.linkedin.com/in/sarahchen9776
- query:
linkedin_id: someone-not-in-specter
matches: []
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
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
````