Making requests

This page explains how to make requests to Linked API, including available endpoints, authorization process, and response structure.

Endpoints

https://api.linkedapi.io/workflows – for executing workflows.

https://api.linkedapi.io/signals – for managing signals (coming soon).

https://api.linkedapi.io/signals/poll – for polling signal events (coming soon).

https://api.linkedapi.io/inbox/poll – for polling the inbox.

https://api.linkedapi.io/network/poll – for polling network events.

https://api.linkedapi.io/stats/actions – for checking API usage statistics.

https://api.linkedapi.io/account – for checking your tokens.

https://api.linkedapi.io/admin/* – for managing your account.

Authorization

Requests to all endpoints except the Admin API must include 2 authorization headers:

  • linked-api-token – your main token that enables overall Linked API access.
  • identification-token – unique token specific to each managed LinkedIn account.

You can obtain these tokens through our platform, as demonstrated below:

Send both tokens as headers with every request:

linked-api-token: your-linked-api-token
identification-token: your-identification-token

Checking your tokens

GET /account returns the name and LinkedIn profile URL of the account the identification token belongs to. It runs no workflow, so it is the quickest way to check that both tokens work. Invalid or missing tokens return the errors any request can return.

curl https://api.linkedapi.io/account \
  -H "linked-api-token: your-linked-api-token" \
  -H "identification-token: your-identification-token"
json
{
  "success": true,
  "result": {
    "name": "John Doe",
    "url": "https://www.linkedin.com/in/john-doe"
  }
}

Response structure

All responses in Linked API have the following structure:

  1. For successful requests:
json
{
  "success": true,
  "result": { /* Endpoint specific result */ }
}
  1. For requests with errors:
json
{
  "success": false,
  "error": { /* Common or endpoint specific error */ }
}