Skip to main content
POST
/
actions
/
salesnavigator-extract-messages
/
run
/
live
Run salesnavigator-extract-messages action live
curl --request POST \
  --url https://api.edges.run/v1/actions/salesnavigator-extract-messages/run/live \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "input": {
    "sales_navigator_thread_url": "<string>",
    "custom_data": {}
  },
  "parameters": {},
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ]
}
'
[ { "sales_navigator_thread_id": null, "delivered_at": null, "first_name": "<string>", "last_name": "<string>", "full_name": "<string>", "linkedin_profile_id": null, "sales_navigator_profile_id": null, "content": "", "message_id": null, "type": "INMAIL", "attachments": [] } ]

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.

Free with Engagement Mode

No credits required when executed with an Engagement Identity. Set type: “engagement” when creating an Identity via API.
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

Query Parameters

​
cursor
string

Cursor value obtained from the X-Pagination-Next response header of a previous request, used to continue pagination. Cursors expire after 24 hours. If a cursor has expired or is invalid, pagination must be restarted from the beginning.

​
page_size
integer
default:20

Maximum number of results per page (read-only; defined by the endpoint, actual count may be lower in some cases like throttling or internal limits).

Required range: 20 <= x <= 20

Body

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

Response

Successful response

​
sales_navigator_thread_id
string
​
delivered_at
string<date-time>
​
first_name
string
​
last_name
string
​
full_name
string
​
linkedin_profile_id
integer
​
sales_navigator_profile_id
string
​
content
string
default:""
​
message_id
string
​
type
enum<string>
default:INMAIL
Available options:
INMAIL,
MESSAGE,
INMAIL_REPLY,
INMAIL_ACCEPT
​
attachments
object[]