LinkedIn reads

LinkedIn public-data reads require linkedin:read. They do not require the caller to submit LinkedIn cookies, proxies, provider keys, or arbitrary user IDs.

Profile

GET /v1/linkedin/profile?url=https://www.linkedin.com/in/example

The identifier can be a supported profile URL, vanity slug, or @handle.

People search

POST /v1/linkedin/search

{
    "filters": {
        "keywords": "founder AI",
        "location": "San Francisco",
        "title": ["CEO", "Founder"],
        "currentCompany": "Ploid",
        "school": "Stanford"
    },
    "limit": 25,
    "cursor": null
}

Recent posts

GET /v1/linkedin/posts?identifier=example&limit=10

Supported read hierarchy

The public LinkedIn surface is intentionally limited to:

• profile details, recent profile posts, and profile comments;
• people search;
• company details and company posts.

Every current route and query parameter is enumerated in the OpenAPI document.

Jobs, groups, ads, services, geographic lookup, reactions, and lead-search endpoints are not part of the public API.

Account-bound actions

Connected-account actions are separate from public-data reads. Mutating actions require a verified connection and an exact human approval where applicable. They are not exposed as a raw cookie or credential passthrough API.