Skip to main content

Account API Documentation

Account API lets you manage LinkedIn accounts programmatically through an API interface. Here, you’ll find an explanation of the API design philosophy and implementation details.

Workflows as basis

Account API is built around the concept of workflows. This means that any automation you want to perform (such as sending a connection request, commenting on a post, retrieving company data, etc.) must be executed as a workflow.

Workflows are constructed using building blocks called actions. Each action represents a specific operation within your workflow. To learn more about this concept, see the actions overview and building workflows pages.

This workflow-based approach, rather than REST-style endpoints, allows you to build any automation sequence imaginable. It provides complete flexibility, which is why we chose workflows as our foundation.

Request timing

Since Account API fully emulates actions of a real LinkedIn user, requests are not executed instantly. For example, simple workflows like visiting a person's page and liking their latest post might take around 20 seconds, while more complex workflows, such as retrieving detailed company information including a list of its employees, can take several minutes.

Sequential execution

Account API executes workflows sequentially. While you can send multiple workflow requests in quick succession, they will not be executed in parallel. Each workflow request is accepted immediately, but its execution will not start until the previous workflow is completed.

For example, if you request a workflow to check a connection status and immediately request another workflow to send a message, the second workflow will begin only after the first workflow is completed.

This approach ensures alignment with realistic user behavior on LinkedIn, as it mirrors how a real user would interact with the platform.

Limits responsibility

Account API does not impose any restrictions to enforce LinkedIn limits, so it is up to you to manage them. LinkedIn limits vary depending on your account's age, social selling index, subscription (e.g., Sales Navigator), and other factors.

You are responsible for following your account's specific limits to avoid potential restrictions.

To help monitor your activity, we have an endpoint to check API usage statistics. We also offer the action for checking your SSI. Additionally, you can explore our guide on understanding LinkedIn limits.

URL normalization

Account API normalizes all LinkedIn URLs in responses, regardless of the format provided in action parameters. Normalized URLs consistently follow these rules:

  • Use https protocol.
  • Include www subdomain.
  • Exclude trailing slash (/).

For example, if action parameters include a URL like http://linkedin.com/in/person1/, the response will return it as https://www.linkedin.com/in/person1. Consider this behavior when implementing URL comparisons or storage in your integration.

Handling missing values

When certain data is unavailable on LinkedIn, some fields in action results may return as null or empty array ([]). Missing fields are always explicitly included in the response rather than being omitted.