JAMF Started rolling out the v3 of their APIs(https://developer.jamf.com/jamf-pro/changelog). As the v1/v2 getting deprecated, when are we updating to v3?Summary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Yes, Jamf has started rolling out the v3 APIs, and the v1 and v2 APIs have been marked as deprecated. Deprecation does not indicate immediate removal; rather, it means that Jamf may stop enhancing or updating those APIs in the future. At present, there is no impact to existing functionality, and the current APIs remain fully operational. Please continue to monitor the SGC Jamf release notes for updates related to the v3 APIs and any associated data or functionality changes. SGC Jamf Release Notes