Skip to main content
POST
/
actions
/
linkedin-comment-post
/
run
/
async
Run linkedin-comment-post action asynchronously
curl --request POST \
  --url https://api.edges.run/v1/actions/linkedin-comment-post/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '{
  "parameters": {},
  "identity_ids": [
    "3c90c3cc-0d44-4b50-8888-8dd25736052a"
  ],
  "identity_mode": "direct",
  "inputs": [
    {
      "linkedin_post_url": "<string>",
      "custom_data": {}
    }
  ],
  "callback": {
    "url": "https://example.com/callback",
    "headers": {}
  }
}'
{
  "run_id": 123,
  "run_uid": "<string>",
  "workspace_uid": "<string>",
  "user_uid": "<string>",
  "action_name": "<string>",
  "status": "pending",
  "postponed_until": "2023-11-07T05:31:56Z",
  "created_at": "2023-11-07T05:31:56Z",
  "synced_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z"
}
To run LinkedIn actions, you must first create an identity and connect a LinkedIn account, either using our Chrome Extension, username/password login, or Rented Accounts for a hassle-free setup.
Callback Delivery: Both async and schedule modes deliver results via the callback URL provided in your request.Consistent Format: All execution modes use the same action logic, so inputs and results are identical regardless of mode.Error Handling: Errors follow the standard API error format.
Using async and schedule modes, you have to implement some kind of callback management. Be sure to check the Managing Callbacks guide to better understand how it works and what your can do.

Authorizations

​
X-API-Key
string
header
required

Body

application/json
​
inputs
object[]
required
Required array length: 1 - 100000 elements
  • Option 1
  • Option 2
​
callback
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.

​
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

Default Response

​
run_id
integer

The ID of the run.

​
run_uid
string

The UID of the run.

​
workspace_uid
string

The UID of the workspace.

​
user_uid
string

The UID of the user.

​
action_name
string

The name of the action.

​
status
enum<string>

The status of the run.

Available options:
pending,
running,
completed,
failed
​
postponed_until
string<date-time> | null

If the run is postponed, this field indicates when it will be retried.

​
created_at
string<date-time>

The date and time when the run was created.

​
synced_at
string<date-time> | null

The date and time when the run was synced.

​
updated_at
string<date-time> | null

The date and time when the run was last updated.

⌘I