Skip to main content
POST
/
flows
/
linkedin-domain-company
/
run
/
async
Run linkedin-domain-company flow asynchronously
curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-domain-company/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "inputs": [
    {
      "domain": "<string>",
      "address": "<string>",
      "custom_data": {
        "meta": "<unknown>"
      }
    }
  ],
  "steps": [
    "linkedin-extract-company"
  ],
  "parameters": {
    "linkedin-find-company-url": {},
    "linkedin-extract-company": {}
  },
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ],
  "identity_mode": "direct",
  "callback": {
    "url": "https://example.com/callback",
    "headers": {},
    "on": "all"
  }
}
'
{
  "uid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "workflow": {
    "uid": "<string>",
    "metadata": {
      "account_rotation": true
    }
  }
}
The LinkedIn Domain to Company flow finds a LinkedIn company page from a company domain or name, then extracts detailed company information. This flow is ideal for company research and enrichment.

​
Flow Steps

The flow executes steps in the following order:
  1. Find LinkedIn Company URL (required): Finds the LinkedIn company page from a domain or company name
  2. Extract LinkedIn Company Profile (optional): Extracts detailed company information
Some steps have dependencies on other 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.
Each item in the inputs array can include an optional custom_data object. The only valid key inside custom_data is meta. Use meta to attach a free-form object (e.g. your own IDs, tags, or context) that will be passed through and available in the flow output.Example:
"inputs": [
  {
    ...
    "custom_data": {
      "meta": {
        "foo": "bar",
        "crm_id": 1234
      }
    }
  }
]
We currently require meta as a workaround to ship this capability; a more solid implementation will follow soon without breaking changes.
Examples: 
curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-domain-company/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "domain": "example.com"
    }
  ],
  "identity_mode": "managed"
}'

curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-domain-company/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "company_name": "Example Inc"
    }
  ],
  "identity_mode": "managed"
}'

curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-domain-company/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "domain": "example.com"
    }
  ],
  "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:
linkedin-extract-company
​
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

​
uid
string<uuid>
​
workflow
object