LinkedIn API
/v2/adCampaignsV2* version retirement
Stopped workingSubscribe to LinkedIn APIShare
Calls to /v2/adCampaignsV2* on LinkedIn API stopped working on December 16, 2024.
Calls it hits
/v2/adCampaignsV2*
What to use instead of these calls
Call the versioned API (/rest/adAccounts/{id}/adCampaigns) with a LinkedIn-Version header (YYYYMM).
In LinkedIn API's words
Developers using LinkedIn Marketing APIs unversioned to migrate to the latest versions. | December 16, 2024 | Deprecated
Facts
- API
- LinkedIn API
api.linkedin.com - Kind
- Version retirement
- Takes effect
- December 16, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against LinkedIn API's own pages
Questions
When does this change take effect?
Calls to /v2/adCampaignsV2* on LinkedIn API stopped working on December 16, 2024.
What happens to calls after December 16, 2024?
They have failed since December 16, 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/adCreativesV2*Version retirement Stopped working -
/v2/organizationalEntityFollowerStatistics*Version retirement Stopped working -
/v2/organizationalEntityShareStatistics*Version retirement Stopped working -
/v2/organizationPageStatistics*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.