Retrieve
People Data API
Retrieve a labeled professional profile from a supported social account.
Input
Profile URL
Account ID
Output
Profile JSON
Professional People Data API
Professional people data, built for developers.
Retrieve profiles, parse resumes, enrich contacts, and turn hiring requirements into structured search criteria with four focused APIs.
Sign in or create an account to get started.
Request
{
"profile_url": "https://www.linkedin.com/in/alex-kim-example"
}{
"info": {
"name": "Alex Kim",
"location": {
"country": "Canada",
"state": "Ontario",
"city": "Toronto"
}
},
"experiences": [
{
"job_title": "Backend Engineer",
"company_name": "Example Labs"
}
]
}
320M+
Professional profiles
190+
Countries / regions
180+
Standardized fields
Daily
Data refresh
< 400 ms
API p95 response
API Suite
Four APIs. One people-data layer.
Retrieve professional profiles, structure resume files, find available contacts, or clarify hiring requirements through a conversation.
Structure
Profile Parsing API
Upload a resume document or image and retrieve labeled profile JSON when processing completes.
Input
PDF
PNG
JPEG
TIFF
Output
Labeled JSON
Connect
Contact Enrichment API
Look up available emails and phone numbers from a supported social account.
Input
LinkedIn
GitHub
Facebook
X
Output
Email
Contact
Clarify
AI People Search API
Turn hiring requirements or JD text into follow-up questions, a role summary, and structured search filters.
Input
Prompt
JD text
Output
Criteria
Role summary
Follow-up
API-Specific Results
One suite. Purpose-built responses.
Each API returns the information its workflow needs: profile data, parsed resume data, contacts, or search criteria. Use the documented response structure for each API rather than assuming one shared person object.
Inputs
LinkedIn URL
Resume document / image
Social account ID
Hiring request / JD text
Social profile URL
ProfileOut APIs
Profiles, contacts, and search criteria
Destinations
CRM
ATS
Data Warehouse
AI Agent
Analytics App
{
"info": {
"name": "Alex Kim",
"location": {
"country": "Canada",
"state": "Ontario",
"city": "Toronto"
}
},
"experiences": [
{
"job_title": "Backend Engineer",
"company_name": "Example Labs"
}
]
}Profile Parsing
Turn resume files into structured profile data.
Upload one supported PDF or image file. ProfileOut extracts and labels the available information and returns JSON when processing completes.
- 01Upload file
- 02Save request ID
- 03Check status
- 04Wait if pending
- 05Read result
- 06Handle missing fields
- 07Save JSON
Resume content
Illustrative file excerpt
Alex Kim · Backend Engineer
Toronto, Canada
Example Labs
Java and Python service development{
"info": {
"name": "Alex Kim"
},
"experiences": [
{
"company_name": "Example Labs",
"job_title": "Backend Engineer"
}
]
}AI People Search
Clarify the people you need, in your own words.
Send a hiring request or JD text. Review a follow-up question, a role summary, and structured filters. The API returns criteria, not candidate profiles or rankings.
Search requirement
Backend engineers in Canada with 5–10 years of experience and Java and Python skills.
filters.data · excerpt
Illustrative
{
"hard_skills": {
"included": [
"Java",
"Python"
],
"not": []
},
"experiences": {
"min": 5,
"max": 10
},
"locations": {
"included": [
{
"value": "Canada"
}
],
"not": []
}
}
Conversation outputs
3 outputs
- Follow-up question Ready
- Role summary Ready
- Search filters Ready
Role summary highlights
- Backend engineering
- Java and Python skills
- 5–10 years of experience
Follow-up
Which product domain is preferred?
Developer Experience
Built to integrate, not evaluate for weeks.
Use server-side REST calls with Bearer authentication. The example submits one People Data request; save request_id and poll the documented GET route when processing is pending.
curl --request POST 'https://api.profileout.com/v1/people-data' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{"profile_url": "https://www.linkedin.com/in/alex-kim-example"}'import requests
response = requests.post(
"https://api.profileout.com/v1/people-data",
headers={"Authorization": "Bearer YOUR_API_KEY"},
json={'profile_url': 'https://www.linkedin.com/in/alex-kim-example'},
timeout=30,
)
response.raise_for_status()
print(response.json()) # Save the ID; check processing status.const response = await fetch("https://api.profileout.com/v1/people-data", {
method: "POST",
headers: {
Authorization: "Bearer YOUR_API_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({"profile_url": "https://www.linkedin.com/in/alex-kim-example"}),
signal: AbortSignal.timeout(30000),
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
console.log(await response.json()); // Save the ID; check status.- Protocol
- REST + JSON
- Authentication
Authorization: Bearer <KEY>- Response model
- API-specific JSON results
- Rate limit
- Limits vary by API; see docs
- Request scope
- One account or file per request
- Retries
- Resume GET polling using the saved ID
- Billing
- One shared credit balance across APIs
Use Cases
Built for products that run on people data.
Use ProfileOut as the professional data layer behind data enrichment, recruiting and HR tech, AI agents and data products, sales intelligence, people-data products and marketplaces, and professional research and talent intelligence.
Data Enrichment
Complete, structure, and enrich professional records already in your systems.
People Data
Contact Enrichment
Recruiting & HR Tech
Build talent workflows with parsed resumes, known-account profiles, and hiring criteria.
People Data
Profile Parsing
AI People Search
AI Agents & Data Products
Give AI systems professional profile context and structured hiring requirements.
AI People Search
People Data
Sales Intelligence
Enrich known professional accounts for research and CRM workflows.
People Data
Contact Enrichment
AI People Search
People-data Products & Marketplaces
Build directories, marketplaces, communities, and discovery products around people data.
Profile Parsing
People Data
AI People Search
Professional Research & Talent Intelligence
Analyze known profiles and structure hiring criteria for your own research tools.
People Data
AI People Search
Usage-Based Pricing
One credit balance. API-specific rates.
Use one shared credit balance across all four APIs. Credits are reserved per request or message and settled under each API’s billing rules.
| Action | Credits | Charging rule |
|---|---|---|
| People Data request | 10 | Per accepted request |
| Profile Parsing file upload | 2 | Per accepted file upload |
| Contact Enrichment request | 15 | Per accepted request |
| AI People Search message | 1 | Per accepted message |
| AI People Search follow-up | 1 | Per accepted follow-up message |
| Failed work | 0 | Reserved credits released |
Data Trust
Evaluate the data before you integrate.
Review coverage, freshness, standardization, and governance as part of your technical evaluation.
Coverage
Available fields depend on the API, the input, and the information available for each record.
Freshness
Freshness varies by record and source. A processing timestamp is not a source-update timestamp.
Standardization
Keep source profile details separate from inferred labels, and handle unavailable values.
Privacy & governance
Review the published data limitations and your responsibilities for storing and using personal information.
Start building with people data.
Retrieve profiles, parse resumes, enrich contacts, and structure hiring requirements with ProfileOut.