Beginning in 2024, new API endpoints and updates will be released on LinkedIn's versioned APIs. Versioning will allow adoption of new API features on your own schedule, requiring less coordination between you and LinkedIn to deliver increased value to our mutual customers, and will also allow more rapid release of new features to LinkedIn's developer platform. Calling versioned APIs requires minor changes to how requests are to LinkedIn are structured. This document describes the changes and provides recommendations for to make adoption of new versions easier.
New Base URL
Versioned APIs will have a new base URL, as described in the table below.
|Old Base URL||New URL|
New Version Header
All requests to versioned APIs will require a new
LinkedIn-Version header, populated with a version identifier.
Example Request with Version Header
GET /rest/someEndpoint HTTP/1.1 Host: api.linkedin.com Linkedin-Version: 20240101
Recommendations for Migration
In order to facilitate easy migration, you should make the base URL and version header configurable modifications to your solution. When new API versions are released, modifying configurations should take minimal time to facilitate adoption of the latest APIs.
Notification to Partners
When new API versions are released, LinkedIn will notify partners through standard communications channels and in our documentation release notes.