Frequently asked questions

No. LinkedIn doesn't provide an official API for user account control and data retrieval. Linked API is an independent product designed to solve this problem. It is not affiliated, associated, authorized, or endorsed by LinkedIn Corporation.

Linked API works with any programming language because it operates through regular HTTP protocol. Additionally, we provide an official Node.js SDK, CLI tool, and MCP server for AI assistants to simplify integration.

Your LinkedIn account interface must be set to English for proper integration with Linked API. We are actively working to expand language support.

Yes. Each account gets a dedicated browser instance – not headless emulation and not an HTTP client pretending to be a browser. It renders pages, executes JavaScript, and behaves exactly like a real desktop browser, matching the type you used during sign-in.

LinkedIn uses two types of profile URLs. A public URL looks like linkedin.com/in/username and is visible on the profile page. A hashed URL looks like linkedin.com/in/ACwAAA... and is an internal identifier. Linked API accepts both formats in action parameters and normalizes all URLs in responses.

Social Selling Index is LinkedIn's metric that measures how effectively you leverage LinkedIn for sales on a scale of 0 to 100. It evaluates four areas: establishing your professional brand, finding the right people, engaging with insights, and building relationships. You can retrieve your current SSI using the st.retrieveSSI action.

A digital fingerprint is a set of browser characteristics – screen resolution, installed fonts, timezone, language, WebGL renderer, and dozens of other parameters – that together create a unique identifier. Linked API creates and maintains a consistent fingerprint for each connected account, matching the characteristics of the device you used during sign-in.

No. To LinkedIn, your activity looks exactly like normal browsing from your own device and location. We use a real browser with your fingerprint, not headless scripts or HTTP requests.

You cannot be blocked for using Linked API itself. However, accounts can still be restricted for spam behavior or exceeding LinkedIn's own limits – which is why we provide configurable rate limits to keep you safe.

No. You enter your password yourself, directly in your isolated cloud browser. We never see, intercept, or store it. After sign-in, the browser stays authenticated using an encrypted session.

Yes. You can configure per-account action limits directly from the platform dashboard. When a workflow contains an action that would exceed a configured limit, the system returns a limitExceeded error instead of executing. This prevents accidental overuse and keeps your account safe.

The system stops execution and returns an error message. No action is performed beyond your configured limits – this protects your account from accidental overuse.

No. Direct access to authenticated sessions is architecturally impossible. Our infrastructure is designed so that no one – including our own engineers – can interact with your LinkedIn account.

One seat equals one connected LinkedIn account. If you automate 3 LinkedIn accounts, you need 3 seats.

Yes. Every new customer can start with a 7-day free trial. Choose Core or Plus and keep the subscription only if Linked API fits your workflow.

Both plans include unlimited workflow execution, all 50+ standard LinkedIn actions, all integrations (n8n, Make), and CLI, MCP & Skills access. Plus adds Sales Navigator actions.

Yes. You can upgrade from Core to Plus or downgrade at any time. Changes take effect on your next billing cycle.

We accept all major credit and debit cards, Apple Pay, Google Pay, and other payment methods supported by Stripe in your region. Invoicing is available for annual plans with 5+ seats.