linkedapi.io valid

Linked API

Secure automation API for LinkedIn – teams and AI agents. Automate messaging, networking, data extraction, and outreach on LinkedIn. Use via API, SDK, CLI, AI agents, or no-code platforms.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T15:30:24.179Z. Cached copy · Source on linkedapi.io

# Linked API

> Secure automation API for LinkedIn – teams and AI agents. Automate messaging, networking, data extraction, and outreach on LinkedIn. Use via API, SDK, CLI, AI agents, or no-code platforms.

Every action runs through a dedicated cloud browser that matches your device, behaves like you, and stays within your limits. Every action you ask Linked API to perform on LinkedIn runs as a workflow composed of actions. Supports both standard LinkedIn and Sales Navigator interfaces.

## Reading this documentation

Every page below under API Reference, SDKs, CLI, MCP Server, the n8n and Make integrations,
Guides, Comparisons, and Optional is available as raw markdown – append `.md` to its URL, or
request the URL with the `Accept: text/markdown` header. Fetch a single page that way instead of
downloading the full dump. Agent Skills entries are landing pages with no markdown source.
The complete documentation in one file: https://linkedapi.io/llms-full.txt

The API Reference is also the SDK and CLI reference. Consecutive code fences marked `tab=HTTP`,
`tab=Node`, `tab=Python` and `tab=CLI` are the same call on each surface (a fence marked
`tab=HTTP,CLI` is the same text for both), and a block between
`:::surface <names>` and `:::` applies only to the surfaces it names. Identifiers in the text
are written as in Node and in HTTP JSON (camelCase); the Python SDK spells methods, parameters and
result attributes in snake_case (`sendMessage` → `send_message`, `reconnectionLink` →
`reconnection_link`), while names inside HTTP JSON stay camelCase.

## API Reference

- [Core Concepts](https://linkedapi.io/docs/core-concepts): This page covers the fundamental concepts and design principles behind Linked API, providing the foundation you need to build effective integrations.
- [Making Requests](https://linkedapi.io/docs/making-requests): This page explains how to make requests to Linked API, including available endpoints, authorization process, and response structure.
- [Data Conventions](https://linkedapi.io/docs/data-conventions): How Linked API represents LinkedIn data in every result: URL normalization, LinkedIn URNs, viewer state, time zones and missing values.
- [Common Errors](https://linkedapi.io/docs/common-errors): Errors any Linked API request can return, with HTTP statuses and fixes – and where errors of workflows, actions and the Admin API are described.
- [Working Hours](https://linkedapi.io/docs/working-hours): This page explains how per-account working hours affect your API requests, what the off-hours policies do, and how to handle a workflow that is parked until the window reopens.
- [Workflows Overview](https://linkedapi.io/docs/workflows-overview): What a workflow is, how long workflows take, and why one account runs its workflows one at a time.
- [Executing Workflows](https://linkedapi.io/docs/executing-workflows): How to execute a workflow: start it, check for its result and cancel it – with request and response formats and the errors
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=linkedapi.io · GET /v1/domain/linkedapi.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for linkedapi.io:
1. POST https://agentwebmap.com/v1/sites/linkedapi.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://linkedapi.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/linkedapi.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/linkedapi.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.