Upgrade headers to versioned API 202208 #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Linkedin API now uses versioning and will deprecate the legacy version on Feb, 28.
I have migrated using
setApiHeaders
, but so not everyone has to read up on this themselves, I am creating this PR.What I have tested already:
Some more testing for deprecations might be needed.
Sources:
https://www.linkedin.com/developers/news/featured-updates/versioning-content-launch
https://learn.microsoft.com/en-us/linkedin/marketing/versioning
For everyone else reading this: