Common Errors

When a request fails, the response has success: false and an error object (see Response structure):

json

{
  "success": false,
  "error": {
    "type": "invalidLinkedApiToken",
    "message": "The provided 'linked-api-token' is invalid."
  }
}

type – the error identifier. Handle errors in your code by type.
message – a human-readable explanation for logs and people.

The same request with an invalid linked-api-token, and the response it gets:

curl -i -X POST https://api.linkedapi.io/workflows \
  -H "Content-Type: application/json" \
  -H "linked-api-token: invalid-token" \
  -H "identification-token: your-identification-token" \
  -d '{"actionType": "st.checkConnectionStatus", "personUrl": "https://www.linkedin.com/in/person1"}'
# HTTP/2 401
# {"success":false,"error":{"type":"invalidLinkedApiToken","message":"The provided 'linked-api-token' is invalid."}}

import { LinkedApiError } from "@linkedapi/node";

try {
  const workflow = await linkedapi.checkConnectionStatus.execute({
    personUrl: "https://www.linkedin.com/in/person1"
  });
} catch (e) {
  if (e instanceof LinkedApiError) {
    console.error(e.type, e.message);
  }
}

from linkedapi import CheckConnectionStatusParams, LinkedApiError

try:
    workflow = linkedapi.check_connection_status.execute(
        CheckConnectionStatusParams(person_url="https://www.linkedin.com/in/person1")
    )
except LinkedApiError as e:
    print(e.type, e.message)

linkedin connection status https://www.linkedin.com/in/person1
echo $?
# stderr: {"error":"invalidLinkedApiToken","message":"The provided 'linked-api-token' is invalid."}
# stderr: Run "linkedin account update" to refresh your tokens.
# 2

Errors any request can return

These errors do not depend on the endpoint: they come from checks every request goes through – authorization and the request rate. Admin API requests do not use the identification-token, so the two errors about it never apply there.

Type	HTTP status	Cause	What to do
`linkedApiTokenRequired`	401	The `linked-api-token` header is missing.	Add the header – see Authorization.
`invalidLinkedApiToken`	401	The `linked-api-token` value matches no token.	Copy the token again from the platform.
`identificationTokenRequired`	401	The `identification-token` header is missing.	Add the token of the LinkedIn account the request is for.
`invalidIdentificationToken`	401	The `identification-token` value matches no LinkedIn account, or the account has been deleted.	Copy the account token again from the platform.
`tooManyRequests`	429	More than 100 requests to one endpoint within 60 seconds with one `linked-api-token`, across all its LinkedIn accounts. Checking a workflow result with `GET /workflows/{workflowId}` allows 600.	Wait and retry. Spread requests over time instead of sending them in bursts.
`unexpectedError`	400	The request failed on the Linked API side.	Retry. If the error repeats, contact support.

The message of each of these errors is fixed text:

Type	`message`
`linkedApiTokenRequired`	`'linked-api-token' is missing in request headers.`
`invalidLinkedApiToken`	`The provided 'linked-api-token' is invalid.`
`identificationTokenRequired`	`'identification-token' is missing in request headers.`
`invalidIdentificationToken`	`The provided 'identification-token' is invalid.`
`tooManyRequests`	`Too many requests. Please try again later.`
`unexpectedError`	`Unexpected error:` – the same for every such failure, without details

Errors described elsewhere

Errors that belong to one part of the API are described next to it:

Starting a workflow – an invalid workflow, a missing subscription or Plus seat, a signed-out account, working hours: Executing Workflows.
Actions inside a workflow – errors an action reports in its result: Actions Overview and each action page.
Signals (coming soon) – Managing Signals.
Webhooks – each method of Managing Webhooks.
Admin API – Admin API Overview.

PreviousData Conventions NextWorking Hours