LinkedIn API sunset version returns 426 error — no automatic fallback to supported version
Version pinning required for LinkedIn Marketing APIs LinkedIn's versioned REST endpoints require a Linkedin-Version header in YYYYMM format. Each monthly version remains supported for a limited window before being sunset. When a request targets a sunset version, the platform responds with a 426-style version-not-supported failure instead of silently routing
linkedin