Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.descovo.com/llms.txt

Use this file to discover all available pages before exploring further.

Live Enrichment fetches the latest data directly from LinkedIn for a specific company or individual profile. Use it when you need up-to-date details for a small number of known targets — for example, verifying a key account’s headcount before outreach, or pulling a prospect’s current title before a call. For bulk enrichment across many records, use the audience workflow instead. Credits are charged per live fetch, for both company and profile requests.

​
Company live enrichment

Fetch real-time data for a single company using its LinkedIn slug, URL, or organization ID. Endpoint: POST /v1/linkedin-live-fetch/company/single Cost: 2 credits per live company fetch.

​
Request parameters

​
apiKey
string
required
Your Descovo API key.
​
type
string
required
The identifier type. One of:
  • "slug" — LinkedIn company slug, e.g. "microsoft" from linkedin.com/company/microsoft/
  • "liUrl" — Full LinkedIn company URL, e.g. "https://www.linkedin.com/company/microsoft/"
  • "orgId" — LinkedIn organization ID (numeric string), or a Descovo company ID that maps to one
​
value
string
required
The identifier value matching the selected type.

​
Example

{
  "apiKey": "sk_live_xxx",
  "type": "slug",
  "value": "microsoft"
}

​
Fallback behavior

If the live fetch fails, the API automatically falls back to a cached database version of the company. When this happens, creditsCharged is 0 — you are only charged when a live fetch succeeds.
If you have a full LinkedIn URL, use type: "liUrl". Descovo extracts the slug or org ID from the URL automatically so you don’t need to parse it yourself.

​
Profile live enrichment

Fetch real-time LinkedIn data for a single professional profile. Endpoint: POST /v1/linkedin-live-fetch/profile/single Cost: 2 credits per live profile fetch.

​
Request parameters

​
apiKey
string
required
Your Descovo API key.
​
identifier
string
required
Any of the following identifier formats:
  • LinkedIn profile slug, e.g. "williamhgates"
  • Full LinkedIn profile URL, e.g. "https://www.linkedin.com/in/williamhgates/"
  • Sales Navigator URN, e.g. "ACwAAA...."
  • LinkedIn user ID (numeric)
​
getDetailedEducation
boolean
default:"false"
When true, the response includes expanded degree and institution data. This increases latency and response size.
​
getDetailedWorkExperience
boolean
default:"false"
When true, the response includes full work history with per-role details. This increases latency and response size.

​
Example

{
  "apiKey": "sk_live_xxx",
  "identifier": "https://www.linkedin.com/in/williamhgates/",
  "getDetailedEducation": false,
  "getDetailedWorkExperience": false
}

​
Fallback behavior

If the live profile fetch fails, the API may:
  • Return a cached database profile with found: true and creditsCharged: 0, or
  • Return found: false if no record exists
You are only charged when a live fetch succeeds.
Setting getDetailedEducation or getDetailedWorkExperience to true increases both response latency and payload size. Only enable these when you specifically need deep education or work history data.

​
When to use live enrichment vs. search APIs

SituationRecommended approach
You have 1–5 specific LinkedIn identifiers and need fresh dataLive enrichment
You need to verify or refresh a key account or prospectLive enrichment
You need to find companies or people matching a set of criteriaCompany Search or People Search
You need to enrich dozens or thousands of recordsAudience workflow
Live enrichment is optimized for targeted, high-value lookups. It is not designed for bulk operations — running it in a loop over large lists is slow and expensive compared to the audience enrichment pipeline.