You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LinkedIn is sunsetting their "unversioned" API and it looks like the update from the unversioned to the versioned API was rolled back in the last commit. Are the plans to implement the updates? It looks like the current end-points will stop working Feb 28.
Per LinkedIn:
In June 2022, we introduced API Versioning and new Content APIs to make it easier for you to build with ease and manage API changes with predictability.
This is a reminder that with the new APIs we plan to sunset and remove the unversioned APIs and legacy Content APIs (eg. Shares API, UGC API) on February 28, 2023.
[Action required] Migrate to the latest versioned API (November 2022) and the new Content APIs using this migration guide.
Learn more about API versioning at LinkedIn and the new APIs through these videos: Versioning, Content APIs. Please submit a Zendesk ticket for any questions.
The text was updated successfully, but these errors were encountered:
LinkedIn is sunsetting their "unversioned" API and it looks like the update from the unversioned to the versioned API was rolled back in the last commit. Are the plans to implement the updates? It looks like the current end-points will stop working Feb 28.
Per LinkedIn:
In June 2022, we introduced API Versioning and new Content APIs to make it easier for you to build with ease and manage API changes with predictability.
This is a reminder that with the new APIs we plan to sunset and remove the unversioned APIs and legacy Content APIs (eg. Shares API, UGC API) on February 28, 2023.
[Action required] Migrate to the latest versioned API (November 2022) and the new Content APIs using this migration guide.
Learn more about API versioning at LinkedIn and the new APIs through these videos: Versioning, Content APIs. Please submit a Zendesk ticket for any questions.
The text was updated successfully, but these errors were encountered: