LinkedIn Talent API versioning

LinkedIn Talent APIs are versioned, so your integrations stay stable while new features are added. New versions are released as updates become available. Use this page to find supported versions, upcoming sunsets, release changes, and migration guidance.

Note

The latest API version is 202603. Use LinkedIn-Version: 202603 in all requests to access the most recent features.

curl -X GET 'https://api.linkedin.com/rest/{resource}' \
-H 'Authorization: Bearer {token}' \
-H 'LinkedIn-Version: 202603'

---

Supported versions

The following table lists all versions and their support status. LinkedIn supports each version for a minimum of 2 years from its release date.

Version	Release Date	Sunset Date	Status
Talent version 202603	Mar 2026	Mar 2028	Active (Latest)
Talent version 202602	Feb 2026	Feb 2028	Active
Talent version 202512	Dec 2025	Dec 2027	Active
Talent version 202511	Nov 2025	Nov 2027	Active
Talent version 202510	Oct 2025	Oct 2027	Active
Talent version 202508.02	Aug 2025	Aug 2027	Active
Talent version 202508	Aug 2025	Aug 2027	Active
Talent version 202507	Jul 2025	Jul 2027	Active
Talent version 202506	Jun 2025	Jun 2027	Active
Talent version 202505	May 2025	May 2027	Active
Talent version 202504	Apr 2025	Apr 2027	Active
Talent version 202503	Mar 2025	Mar 2027	Active
Talent version 202501	Jan 2025	Jan 2027	Active

---

How versioning works

Version header

All requests must include the LinkedIn-Version header. The value identifies the API version and uses YYYYMM format for standard releases or YYYYMM.xx for patch releases.

-H 'LinkedIn-Version: 202603'

Version and base path

Versioned APIs use the https://api.linkedin.com/rest/ base path. Legacy unversioned APIs use https://api.linkedin.com/v2/. As versioned replacements are released, the corresponding legacy endpoints will be sunset.

Release cadence

LinkedIn publishes new API versions as updates are ready. Patch versions (e.g., 202508.02) are issued for critical security, privacy, or bug fixes only.

Support window

Each version is supported for a minimum of 2 years from its release date. You can stay on any supported version within that window, but migrating to the latest version gives you the longest support window and access to all new features.

Versioned API docs

Use the version dropdown selector to view the API updates applicable to a specific version.

---

API version history

Version	Status	APIs updated	Summary of changes	Release notes
Talent version 202603	Active (Latest)	PUT /rest/candidatePipelines DELETE /rest/candidatePipelines PUT /rest/pipelineStages DELETE /rest/pipelineStages PUT /rest/candidatePipelineStages DELETE /rest/candidatePipelineStages	CRM Connect: CRM candidate pipelines and pipeline stages APIs migrated to versioned REST endpoints (new external* field names)	CRM Connect
Talent version 202602	Active	DELETE /rest/candidates	Data Deletion: Delete Candidates migrated to new versioned endpoint; externalCandidateId and integrationContext replace legacy atsCandidateId and dataProvider	RSC
Talent version 202512	Active	—	No new endpoints	RSC
Talent version 202511	Active	—	No new endpoints	RSC
Talent version 202510	Active	PUT /rest/candidateNotes DELETE /rest/candidateNotes DELETE /rest/applicationNotes DELETE /rest/attachments	Candidate Notes new REST endpoint; Delete Candidate Notes, Delete Application Notes, and Delete Document (Resume) endpoints introduced; exported candidate location updated to structured object	RSC
Talent version 202508.02	Active	DELETE /rest/applicationInterviewFeedbacks	Patch: Delete Application Interview Feedback migrated to versioned REST endpoint	RSC
Talent version 202508	Active	PUT /rest/attachments DELETE /rest/attachments	New Attachments endpoint introduced for syncing resumes as attachments	RSC
Talent version 202507	Active	PUT /rest/applicationStage DELETE /rest/applicationStage GET /rest/exportedCandidates GET /rest/atsPurgedExportedCandidates DELETE /rest/atsApplications GET /rest/exportedApplicationEvaluations GET /rest/simpleJobPostings GET /rest/simpleJobPostingStatus GET /rest/simpleJobPostingTasks DELETE /rest/jobRequisitions DELETE /rest/jobRequisitionStages	Sync Application Stages, Exported Candidates, Purged Exported Candidates, and Application Evaluations migrated or introduced as REST endpoints; Simple Job Postings endpoints migrated to REST; referenceEntityType and referenceEntityId added to exported candidates response; Delete endpoints introduced for job requisitions and stages	RSC
Talent version 202506	Active	—	Sync Job Requisitions: hiredCount and ownerType fields added	RSC
Talent version 202505	Active	—	No new endpoints	RSC
Talent version 202504	Active	PUT /rest/jobRequisitions PUT /rest/jobRequisitionStages	Sync Job Requisitions and Sync Job Requisition Stages REST endpoints introduced	RSC
Talent version 202503	Active	—	No new endpoints	Talent
Talent version 202501	Active	—	Initial versioned API release under new https://api.linkedin.com/rest/ base path	Talent

---

Upcoming sunsets

Plan your migrations before these dates to avoid service disruptions.

Version	Sunset Date
Talent version 202501	Jan 2027
Talent version 202503	Mar 2027
Talent version 202504	Apr 2027
Talent version 202505	May 2027
Talent version 202506	Jun 2027
Talent version 202507	Jul 2027
Talent version 202508	Aug 2027
Talent version 202508.02	Aug 2027
Talent version 202510	Oct 2027
Talent version 202511	Nov 2027
Talent version 202512	Dec 2027
Talent version 202602	Feb 2028
Talent version 202603	Mar 2028

---

Migrating between versions

When migrating between REST API versions, update the LinkedIn-Version header value to the target version. No URL changes are required unless an endpoint path itself changed (see the API Version History table above). When migrating from legacy https://api.linkedin.com/v2/ endpoints, you must also update the base path to https://api.linkedin.com/rest/ and, in some cases, use updated endpoint paths.

# Before
-H 'LinkedIn-Version: 202510'

# After
-H 'LinkedIn-Version: 202603'

Review the Summary of Changes column in the API version history table for each version between your current and target version to identify any new required fields or endpoint changes.

Breaking change policy

LinkedIn may release a patch version to address critical security, privacy, or bug fix issues. These cases are rare, and LinkedIn works closely with partners to minimize disruption when they occur.

---

FAQ

What happens if I use a sunset version?

Requests will return a 426 Upgrade Required error:

{
    "error": "Unsupported API version",
    "message": "The API version you are using has been sunset. Please upgrade to a supported version."
}

Which version should I migrate to?

Always migrate to the latest version listed in the Supported versions table. It provides the longest support window and access to all current features.

How do I know what changed between versions?

Refer to the API version history table and the linked program-level release notes for each version.