HTTP 426 Upgrade Required on missing LinkedIn-Version header
0 reputation · 16 Apr 2022, 23:50 UTC
LinkedIn's REST APIs utilize a date-based versioning system via the LinkedIn-Version header (formatted as YYYYMM). This mechanism ensures that partner applications remain pinned to specific API behaviors, as the platform progressively retires legacy, unversioned endpoints and deprecated version cycles.
When an application sends a request without the required version header, or utilizes a version that has passed its sunset date, the API returns a 426 Upgrade Required or related 4xx error. This behavior creates a hard breaking change for integrations that do not actively manage the versioning lifecycle.
Integrators face a conflict between maintaining environment stability through pinning and avoiding the risk of sudden service failure at sunset. There is no automated fallback to the latest stable version if the pinned version exceeds the deprecation window defined in the developer documentation.
- What is the recommended strategy for programmatically detecting upcoming version sunset dates before a hard failure occurs?
- Does the LinkedIn API provide a specific header or payload in the response body to signal that a pinned version is approaching its deprecation deadline?
linkedin