API reference

API reference

47 GET endpoints across 5 capability families, generated from the checked-in OpenAPI 3.1.0 document. Every endpoint returns the same response envelope and authenticates with the X-API-Key header.

  • 47Documented endpoints
  • 6Open without an account
  • GETEvery request, no side effects

Every route is listed on this page. 6 endpoints are documented in full — parameters, response codes, and request samples — for everyone; the other 41 open once you log in.

Endpoint families

5 families

Endpoints are grouped by the object they read. Pick a family to jump to its full list, or search the sidebar by path — a query like by-domain or jobs/search matches the route directly.

5 families47 endpoints1 response envelope

What each page documents

Per endpoint

Every endpoint page is generated from the same OpenAPI document, so it carries the same five parts in the same order. Nothing below is hand-maintained, and nothing drifts from the running API.

Route
method + pathThe HTTP verb and full path, ready to paste after the base URL.
Parameters
tableEvery path and query parameter with its type, constraints, and whether it is required.
Response codes
tableThe status codes the endpoint returns and what each one means.
Request samples
curl · Node · PythonA runnable call in three languages, with the key read from the environment.
Response example
jsonThe success envelope for that endpoint. Synthetic data — no real records appear in these docs.

Running a call always needs a key — see Authentication for how to get one and send it safely.

Profile

1 of 22 open

LinkedIn v2 profile lookup, contact, and activity endpoints. Profile path inputs accept public /in/ identifiers; full profile URLs use the dedicated url query parameter endpoints.

Company

2 of 11 open

LinkedIn v2 company and organization page endpoints. Company inputs accept /company/ universal names; full company URLs use the dedicated url query parameter endpoints.

0 of 8 open

LinkedIn v2 people, company, content, hashtag, and filter search endpoints. Dynamic filter values come from /api/v2/search/filters.

Job

3 of 3 open

LinkedIn v2 job search, filters, feeds, company jobs, and detail endpoints. Dynamic job filter values come from /api/v2/jobs/search/filters.

Post

0 of 3 open

LinkedIn v2 post detail and social endpoints. Post social endpoints need the full /posts/<slug> slug, not only a numeric id.