Skip to main content
POST
/
flows
/
linkedin-people-enrich
/
run
Run linkedin-people-enrich flow asynchronously
curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-people-enrich/run \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "inputs": [
    {
      "linkedin_profile_url": "<string>"
    }
  ],
  "steps": [
    "Extract LinkedIn Company Profile"
  ],
  "parameters": {
    "linkedin-extract-people": {},
    "linkedin-extract-company": {},
    "fullenrich-enrich-people": {}
  },
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ],
  "identity_mode": "direct",
  "callback": {
    "url": "https://example.com/callback",
    "headers": {}
  }
}
'
{
  "id": 123,
  "uid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "workflow": "<unknown>"
}
The LinkedIn People Enrich flow extracts detailed information from a LinkedIn profile, then optionally enriches it with company data and contact information. This flow is ideal for profile enrichment and contact discovery.

​
Flow Steps

The flow executes steps in the following order:
  1. Extract LinkedIn People Profile (required): Extracts detailed information from the specified LinkedIn profile
  2. Optional enrichment steps (can include any combination):
    • linkedin-extract-company: Extracts company information for the profile’s current company
    • fullenrich-enrich-people: Enriches the profile with contact information (emails and/or phone numbers). Credit costs: 2 credits for emails, 20 credits for phones, 22 credits for both.
Some steps have dependencies on other steps. For example, fullenrich-enrich-people requires profile data from previous steps. If you include a step that has dependencies, the required steps will be automatically activated even if you don’t explicitly include them in your request body.
Examples: 
curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-people-enrich/run \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "linkedin_profile_url": "https://www.linkedin.com/in/example-profile"
    }
  ],
  "identity_mode": "managed"
}'

curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-people-enrich/run \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "steps": [
    "Extract LinkedIn Company Profile",
    "Full enrich people"
  ],
  "parameters": {
    "linkedin-extract-people": {
      "sections": true,
      "experiences": true,
      "skills": true,
      "highlights": true
    },
    "fullenrich-enrich-people": {
      "enrich_level": "emails_and_phones"
    }
  },
  "inputs": [
    {
      "linkedin_profile_url": "https://www.linkedin.com/in/example-profile"
    }
  ],
  "identity_ids": ["44444444-4444-4444-4444-444444444444"]
}'

curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-people-enrich/run \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "linkedin_profile_url": "https://www.linkedin.com/in/example-profile"
    }
  ],
  "identity_mode": "managed",
  "callback": {
    "url": "https://your-app.com/webhook/flow-results",
    "headers": {
      "Authorization": "Bearer your-webhook-token"
    }
  }
}'
Instead of polling for results, you can use webhooks to receive automatic notifications when this flow completes. Learn more about webhook payloads and handling.

Authorizations

​
X-API-Key
string
header
required

Body

application/json
​
inputs
object[]
required
Required array length: 1 - 1000 elements
​
steps
enum<string>[]

Optional list of step to run. If not provided, only the required steps will be run.

Available options:
Extract LinkedIn Company Profile,
Full enrich people
​
parameters
object
​
identity_ids
string<uuid>[] | null

An array of Identity UUIDs linked to identities (e.g. LinkedIn) used to execute the Action. You must provide at least one valid UID with access to the integration. Do not use account_uid values — only user_uid is supported.

Example:
["44444444-4444-4444-4444-444444444444"]
​
identity_mode
enum<string> | null
default:direct

If "auto", the Action will use any identities from the current workspace (unless you have provided a list of identity_ids). "managed" will use the Edges pool of identities for an extra credit cost

Available options:
direct,
auto,
managed
​
callback
object

Response

Successful response

Successful response

​
id
integer
​
uid
string<uuid>
​
workflow
any