Skip to main content
POST
/
actions
/
linkedin-extract-event
/
run
/
live
Run linkedin-extract-event action live
curl --request POST \
  --url https://api.edges.run/v1/actions/linkedin-extract-event/run/live \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "input": {
    "linkedin_event_url": "<string>",
    "custom_data": {}
  },
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ],
  "identity_mode": "direct"
}
'
{
  "event_name": "<string>",
  "event_information": "<string>",
  "linkedin_event_id": "<string>",
  "linkedin_event_url": "<string>",
  "event_external_link": "<string>",
  "created_at": "2023-11-07T05:31:56Z",
  "number_attendees": "<string>",
  "event_start_datetime": "<string>",
  "event_end_datetime": "<string>",
  "company_name": "<string>",
  "linkedin_company_id": "<string>",
  "linkedin_company_url": "<string>",
  "first_name": "<string>",
  "last_name": "<string>",
  "full_name": "<string>",
  "speakers": [
    {
      "first_name": "<string>",
      "last_name": "<string>",
      "full_name": "<string>",
      "linkedin_profile_url": "<string>"
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.edges.run/llms.txt

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

To run LinkedIn actions, you must first create an identity and connect a LinkedIn account, either using our Chrome Extension, username/password login, or Managed Accounts for a hassle-free setup.

Authorizations

​
X-API-Key
string
header
required

Body

application/json
​
input
object
required
​
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

Response

Successful response

​
event_name
string
​
event_information
string
​
linkedin_event_id
string
​
linkedin_event_url
string<uri>
​
event_external_link
string<uri>
​
created_at
string<date-time>
​
number_attendees
string
​
event_start_datetime
string
​
event_end_datetime
string
​
company_name
string
​
linkedin_company_id
string
​
linkedin_company_url
string<uri>
​
first_name
string
​
last_name
string
​
full_name
string
​
speakers
object[]