Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Overview
LinkedIn is committed to continuously evolving its product offerings. To support our API partners in this journey, we provide the necessary tools and experiences to enable ongoing innovation and the delivery of optimal solutions to our mutual customers.
We recognize the importance of stable API integrations and the need for clear guidance on planning and implementing changes. Our partners frequently experiment, build, test, and deploy new products.
To facilitate this, we are introducing API versioning within the LinkedIn Talent API Program. This ensures that your active integrations remain functional while you work on incorporating our latest updates.
What’s changing?
LinkedIn’s Talent APIs are transitioning to a versioned API release cycle starting with the January 2025 release under a new base path: https://api.linkedin.com/rest/.
Key changes include:
- New Base Path: The versioned APIs will use
https://api.linkedin.com/rest/instead of the legacyhttps://api.linkedin.com/v2/. - Quarterly Release Cycle: Versioned API releases will occur quarterly, with each release named after the month when development began.
- Sunsetting Legacy APIs: Legacy (unversioned) Talent APIs using the
https://api.linkedin.com/v2/base path will be sunset as new versioned APIs are released. - Version Indication via HTTP Headers: API clients must use HTTP headers to specify the API version they are targeting.
- Comprehensive Documentation: Each version will be accompanied by detailed documentation and change guides.
- Support Duration: Versioned Talent APIs will be supported and stable for a minimum of one year before being sunset.
These changes aim to provide a more predictable and stable integration experience for our API partners.
Latest Version
| Version Name | Version Header |
|---|---|
| April 2025 | 202504 |
Technical documentation
LinkedIn’s Talent API Program supports versioning so API partners can release changes over time. This document explains how to use versioned APIs.
How your API client should use versioning
HTTP headers will be used for clients to indicate which API version implementation they expect. Include a request header with the key “LinkedIn-Version” and set the value to the version (format: YYYYMM) to correspond with the documentation version you’re referencing, for example - “LinkedIn-Version: 202501 would indicate that you are using the version published in the month of April.
curl -X POST 'https://api.linkedin.com/rest/simpleJobPostings' \
-H 'Authorization: Bearer {INSERT_TOKEN}' \
-H 'Content-Type: application/json' \
-H 'Linkedin-Version: 202501’
Version Headers
In many cases, the URL resource paths your integration uses may not change across versions, but the behavior of the individual API methods will. For example, there may be new parameters required or new fields available on the response schemas.
The API changes must include the Version Header for the version (release) that needs to be adopted. For example, for the January 2025 Release, the versioned header would be: "LinkedIn-Version": "202501"
Version headers are tied to the Release date:
| Version | Version Header Values |
|---|---|
| January 2025 | "LinkedIn-Version": "202501" |
| April 2025 | "LinkedIn-Version": "202504" |
Versioned API Docs
Each version of the LinkedIn Talent API Program has distinct and comprehensive documentation covering all supported APIs. It also includes a changelog indicating all changes from the previous version, specifying which resources have been updated or added. The dropdown selector can be used to view updates for a particular version, including both versioned and unversioned content.
Version Cadence
LinkedIn Talent API Program will publish new versions quarterly, and each version will be supported for a minimum of 1 year. For example, the January 2025 release will be supported through January 2026 before it is sunset.
Individual API resources may evolve at different times (e.g., a job posting API may be updated one quarter a year). Each API resource will have its own migration guide to help you navigate major updates.
You can choose to integrate with the newest API changes as soon as they’re released or wait until you’re ready, as long as it’s within the one-year support window.
Expectations
Keep up with us
LinkedIn expects that our LinkedIn Talent API Program API partners work to deliver the latest and most valuable experiences to our customers within a reasonable time of their availability. As a result, we will sunset our API versions as early as one year after release.
Breaking Change Exceptions
At times, LinkedIn may need to change APIs within the supported stable window.
LinkedIn reserves the right to release a patch version to any API if required for any critical security or privacy issues or bug fixes. While the likelihood of these scenarios is minimal, we will work closely with partners to minimize the impact of any breaking changes.
FAQ
Which versions can I use?
You can use any version that hasn’t been sunset. The documentation will reflect all available API versions. Migrating to the latest version, however, comes with two important benefits:
- You can take advantage of all of our latest features.
- You have the option to wait up to a full year before having to migrate again.
What about other LinkedIn APIs outside of Talent?
At present these APIs are unversioned, which may be subject to change at any time at the discretion of product ownership teams.
How do I migrate from an older API version to a later version?
To migrate your app from an older version to a later version, simply update the older version‘s YYYYMM formatted value in the header to the later version’s value. For example, here’s how you’d migrate from the January 2025 version to the April 2025 version.
-H `Linkedin-Version: 202501` to -H `Linkedin-Version: 202504`
Reasons for migrating to a later version include:
- Avoiding service disruptions; it's important to upgrade to a newer supported version before the older version is no longer supported (we’ve committed to supporting each version for a minimum of one year).
- Utilizing new features that are not accessible in the older version.
Which version of the API should I migrate to?
While you can migrate to any later version of the API, migrating to the latest version comes with two important benefits:
- You can take advantage of all of our latest features.
- You have the option to wait up to a full year before having to migrate again.
What happens if I don’t migrate before a version is sunset?
If you continue using a version after it’s been sunset, you may encounter errors indicating that the version is no longer supported, such as a "426 Upgrade Required" response with a message like:
{
"error": "Unsupported API version",
"message": "The API version you are using has been sunset. Please upgrade to a supported version."
}