LinkedIn API

Public-data LinkedIn endpoints.

When To Use This API

The LinkedIn API is for agent workflows that need public, platform-native data without writing a custom collector for every task. Use it when a prompt needs evidence from live social records, when a Skill needs repeatable enrichment, or when product code needs the same contract an agent discovered through MCP.

This section lists 8 live LinkedIn operations from the canonical OpenAPI spec. Each operation page documents the route, method, parameters, response envelope, pagination behavior when available, and the error vocabulary shared across UnifAPI.

• Enrich public people, companies, jobs, and posts when a research agent needs business context.
• Build lead, hiring, or competitive-intelligence workflows from browser-visible LinkedIn identifiers.
• Connect company pages, public posts, reactions, comments, and search results without custom scraping code.

Agent Contract Notes

Agents usually discover these endpoints with the hosted UnifAPI MCP server, inspect the operation schema, then call only the records needed for the current task. Developers can call the same endpoints over HTTP with an API key, which makes the path from exploratory agent run to production integration direct.

Every successful response uses a stable envelope with a request id, data payload, optional pagination cursor, and billing metadata. Errors use the same closed vocabulary across platforms, so retry logic, user-facing explanations, and cost reporting can stay consistent even when a workflow spans multiple public-data sources.

When you are choosing an operation, start from the public identifier the user already has: a profile username, post id, channel id, subreddit name, search term, or URL-derived slug. Prefer the narrowest endpoint that answers the question, then expand only when the agent needs more evidence. This keeps record usage predictable, makes citations easier to explain, and avoids turning a focused research task into an expensive crawl.

Operations

Companies

• GET /linkedin/companies/{slug}/posts — List posts published by a LinkedIn company page — Return posts published from a LinkedIn company page by URL slug as a cursor-paginated list.
• GET /linkedin/companies/{slug} — Get a LinkedIn company profile by URL slug — Return a canonicalized LinkedIn company profile by its URL slug (universal_name, e.g.

Jobs

• GET /linkedin/jobs/{id} — Get a LinkedIn job posting by ID — Return a LinkedIn job posting by ID, including title, company, location, description, and optional skills or hiring-team data.

Posts

• GET /linkedin/posts/{id}/comments — List top-level comments on a LinkedIn post — Return top-level comments on a LinkedIn post by activity ID as a cursor-paginated list.
• GET /linkedin/posts/{id} — Get a LinkedIn post by ID — Return a single LinkedIn post by its numeric ID, including author, text, media, and engagement counts.

Search

• GET /linkedin/search/jobs — Search LinkedIn jobs by keyword and filters — Search LinkedIn job postings by keyword and filters as a cursor-paginated list.

Users

• GET /linkedin/users/{username}/posts — List posts authored by a LinkedIn user — Return posts authored by a LinkedIn user from the profile URL slug as a cursor-paginated list.
• GET /linkedin/users/{username} — Get a LinkedIn user profile by URL slug — Returns the canonical LinkedIn profile for the given URL slug (public_identifier).