LinkedIn API
/202311/* version retirement
Stopped workingSubscribe to LinkedIn APIShare
On November 15, 2024, API version /202311 was retired. Requests sent to /202311/* endpoints fail after this date. Calls targeting this version no longer succeed.
Calls it hits
/202311/*
What to use instead of these calls
Migrate to the latest API version launched today.
In LinkedIn API's words
202311 - Nov 15, 2024
Facts
- API
- LinkedIn API
api.linkedin.com - Kind
- Version retirement
- Takes effect
- November 15, 2024
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against LinkedIn API's own pages
Questions
When does this change take effect?
Calls to /202311/* on LinkedIn API stopped working on November 15, 2024.
What happens to calls after November 15, 2024?
They have failed since November 15, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from LinkedIn API 10
-
/202306/*Version retirement Stopped working -
/202307/*Version retirement Stopped working -
/202312/*Version retirement Stopped working -
/v2/adAccountsV2*Version retirement Stopped working -
/v2/adAnalyticsV2*Version retirement Stopped working -
/v2/adCampaignGroupsV2*Version retirement Stopped working -
/v2/adCampaignsV2*Version retirement Stopped working -
/v2/adCreativesV2*Version retirement Stopped working -
/v2/organizationalEntityFollowerStatistics*Version retirement Stopped working -
/v2/organizationalEntityShareStatistics*Version retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.