# API Versions and Deprecation to Retired Timeframe **URL:** \ **Category:** Questions\ **Created:** [October 4, 2021, 9:03pm UTC](https://developer.squareup.com/forums/t/api-versions-and-deprecation-to-retired-timeframe/3846 "2021-10-04T21:03:36Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![joel.h](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/joel.h/32/824_2.png) [@joel.h](https://developer.squareup.com/forums/u/joel.h)\ **Post date:** [October 4, 2021, 9:03pm UTC](https://developer.squareup.com/forums/t/api-versions-and-deprecation-to-retired-timeframe/3846/1 "2021-10-04T21:03:36Z")
I’m needing to upgrade my API version to utilize some new abilities and had a couple questions: 1. Is there a general timeframe of when a deprecated call will move to “Retired” status, or does it change depending on the call? 2. API app version vs. Auth header version: What’s the actual difference in changing the API version in the auth header to upgrading the API version for the “app” in the dashboard? I was able to change the version in the auth header and make calls without changing the app API version - so I’m not sure what all each impacts. Any insight here would be greatly appreciated. Thanks! ---
**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\ **Post date:** [October 4, 2021, 11:11pm UTC](https://developer.squareup.com/forums/t/api-versions-and-deprecation-to-retired-timeframe/3846/2 "2021-10-04T23:11:44Z")
With [Square’s API life cycle](https://developer.squareup.com/docs/build-basics/api-lifecycle) deprecated is the first stage toward retirement. They are typically deprecated at least 12 months before permanent retirement. Deprecated functionality remains publicly available and fully supported, but its use is strongly discouraged for all applications, regardless of the `Square-Version` provided with API calls. You are discouraged from building new solutions with deprecated APIs. On deprecation, you should plan on updating existing applications that depend on the deprecated APIs. The Auth header version overrides the default by explicitly specifying an API version in a request by adding the `Square-Version` request headers. This enables developers to test different API versions. 🙂 ---
**Author:** ![Hall](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/hall/32/834_2.png) [@Hall](https://developer.squareup.com/forums/u/Hall)\ **Post date:** [October 8, 2021, 7:41pm UTC](https://developer.squareup.com/forums/t/api-versions-and-deprecation-to-retired-timeframe/3846/3 "2021-10-08T19:41:53Z")
> [@Bryan-Square](#): > > With [Square’s API life cycle](https://developer.squareup.com/docs/build-basics/api-lifecycle) deprecated is the first stage toward retirement. They are typically deprecated at least 12 months before permanent retirement. > > Deprecated functionality remains publicly available and fully supported, but its use is strongly discouraged for all applications, regardless of the `Square-Version` provided with API calls. You are discouraged from building new solutions with deprecated APIs. On deprecation, you should plan on updating existing applications that depend on the deprecated APIs. > > The Auth header version overrides the default by explicitly specifying an API version in a request by adding the `Square-Version` request headers. This enables developers to test different API versions. 🙂 Every _API_ integration ages slowly over time, and eventually has a " _retirement_ date" lurking somewhere in the (hopefully) distant future.