Skip to main content
​
New

​
Week of July 31

​
New: Job Details endpoint

Job Details returns a single LinkedIn job posting from its ID or URL: title, full description, location, employment type, seniority, workplace type, salary when published, posting and expiry dates, application counts and the hiring company.
Two optional sections, each an extra 1 credit charged only when it returns data:
  • include_company — the hiring company’s description, employee count, specialities, headquarters address and cover image
  • include_hiring_team — the job poster and recruiters listed on the posting, with profile URLs and photos
A base request costs 1 credit; both flags together cost 3. A section that could not be retrieved comes back as null and is not charged, and failed requests are never charged.Every response returns the same set of fields whichever options you send — a field that a given request cannot fill is null rather than absent, so parsing code never has to branch.
​
Improved

​
Week of July 25

​
Standardized endpoint paths

All data endpoints now live directly under /api/v1/ — for example POST /api/v1/person, POST /api/v1/company, POST /api/v1/post/comments, and POST /api/v1/salesnavigator/search. The documentation and OpenAPI specs now reference the new paths everywhere.No action required: every previous path (e.g. POST /api/v1/linkedin/person) remains fully supported as a permanent alias, with identical request and response formats, authentication, and credit costs. Existing integrations continue to work unchanged.
​
New

​
Week of July 4

​
New: People profile enrichment flags

The People endpoint now supports seven optional enrichment flags, each appending an additional data section to the profile response for an extra 2 credits (charged only on success):
  • company_interest — companies the profile follows
  • top_voices_interest — LinkedIn Top Voices the profile follows
  • group_interest — LinkedIn Groups the profile belongs to
  • school_interest — schools the profile follows
  • newsletter_interest — LinkedIn Newsletters the profile is subscribed to
  • similar_profiles — profiles similar to this one
  • recommendations_data — full profile bundle plus recommendations given/received
All enrichment requests retry automatically on transient upstream failures. If an enrichment fails after retries, the base profile response still succeeds and the field contains a generic error instead of upstream details — no credit is charged for a failed enrichment.

​
New: Company insights flag

The Company endpoint now supports an optional company_insights flag, appending an insights section to the response for an extra 10 credits (charged only on success): headcount trends, hiring trends, notable alumni, job openings by function, and median employee tenure. Retried automatically on transient upstream failures; a failed insights request returns a generic error in insights and is not charged.