Use this when you need the freshest possible person data — for time-sensitive outreach, verifying stale profiles, or fetching data not yet in the cached database.
The Person Live Fetch API scrapes a person’s LinkedIn profile on demand and returns fresh data. Use this sparingly — it is slower and more expensive than cached Enrich.
POST https://api.crustdata.com/person/professional_network/enrich/live
Replace YOUR_API_KEY in each example with your actual API key. All requests require the x-api-version: 2025-11-01 header.
Fetch a person profile in real-time
curl --request POST \
--url https://api.crustdata.com/person/professional_network/enrich/live \
--header 'authorization: Bearer YOUR_API_KEY' \
--header 'content-type: application/json' \
--header 'x-api-version: 2025-11-01' \
--data '{
"professional_network_profile_urls": [
"https://www.linkedin.com/in/abhilashchowdhary"
]
}'
Response trimmed for clarity. The full response includes skills, employment details, education, contact info, and more.
Fetch with specific fields
Use the fields parameter to limit which sections are returned:
curl --request POST \
--url https://api.crustdata.com/person/professional_network/enrich/live \
--header 'authorization: Bearer YOUR_API_KEY' \
--header 'content-type: application/json' \
--header 'x-api-version: 2025-11-01' \
--data '{
"professional_network_profile_urls": [
"https://www.linkedin.com/in/abhilashchowdhary"
],
"fields": ["basic_profile", "professional_network", "contact"]
}'
Live Fetch vs Enrich
| Live Fetch | Enrich |
|---|
| Endpoint | /person/professional_network/enrich/live | /person/enrich |
| Data source | Live LinkedIn scrape | Crustdata cached database |
| Freshness | Real-time (seconds old) | Cached (periodically updated) |
| Latency | Higher (live scraping) | Lower (pre-indexed) |
| Response | Top-level array | Top-level array |
| Best for | Stale profile refresh, missing data | General enrichment, batch workflows |
Use Live Fetch sparingly — it is slower and more expensive than cached Enrich. For most workflows, cached Enrich provides sufficiently fresh data.
Request parameters
| Parameter | Type | Required | Description |
|---|
professional_network_profile_urls | string[] | Yes | LinkedIn profile URLs to fetch. Max 25. |
fields | string[] | No | Specific field groups to include in the response. |
Errors
| Status | Meaning |
|---|
400 | Invalid request — malformed URL or missing identifier. |
401 | Invalid or missing API key. |
403 | Permission denied or insufficient credits. |
404 | Profile not found on LinkedIn. |
500 | Internal server error. Retry with exponential backoff. |
API reference summary
| Detail | Value |
|---|
| Endpoint | POST /person/professional_network/enrich/live |
| Auth | Bearer token + x-api-version: 2025-11-01 |
| Request | professional_network_profile_urls (required). Optional: fields. |
| Response | Array: [{ "matched_on", "match_type", "matches": [{ "confidence_score", "person_data" }] }] |
| Errors | 400, 401, 403, 404, 500 |
What to do next
