Square API Lifecycle
This document outlines the lifecycle for Square APIs and establishes expectations for the various stages of development.
Square currently supports 2 API sets:
Connect v1 APIs — The original API set released in 2014, currently being retired.
Square APIs — The current API set, previously known as Connect v2.
Square APIs typically follow a path from Alpha, to Beta, to General Availability (GA) before Deprecation and Retirement. Deprecated functionality typically remains publicly available for 12 months before Square retires the functionality.
Beta code is considered stable and production ready but may not have all the functionality intended for final release. Beta functionality is publicly available and breaking changes follow the normal Square API versioning process. Beta functionality is documented and clearly tagged in the Technical Reference section of the Developer resource site. More expansive beta releases (e.g., new core functionality, new APIs) are also covered in the Documentation section of the Developer resource site.
GA code is considered stable, polished, and production ready. GA functionality is publicly available and breaking changes follow the normal Square API versioning process. GA functionality is documented in the Technical Reference section and Documentation sections of the Developer resource site.
Deprecated functionality remains publicly available but use is strongly discouraged for all applications, regardless of the Square-Version provided during API calls. Deprecated functionality is clearly tagged in the Documentation section and grouped together in the Technical Reference section of the Developer resource site. Deprecated APIs typically provide a 12-month support period before permanent retirement.
Square strongly encourages existing users to migrate to the applicable replacements as soon as possible to avoid disrupting their users. Developers using Square SDKs release on, or after, the deprecation date will see deprecation warnings in their logs (for interpreted languages) or compilation warnings (for compiled languages) when referencing deprecated functionality.
Retired code is unavailable to all applications regardless of the
Square-Version provided during API calls. REST API calls return errors for all users and retired functionality is removed from all SDKs released on, or after, the retirement date. Information on retired functionality is removed from the Technical Reference and Documentation sections of the Developer resource site. Retired functionality may still appear in archived versions of the Technical Reference, but cannot be accessed, even by applications still pinned to an older
The following APIs are deprecated in their entirety and currently scheduled for retirement. All endpoints and related data types will retire on the date noted below. See the associated migration guide for guidance.
|V1Employees.Employees||pending||Work in progress||TBD||TBD|
|V1Employees.EmployeeRoles||pending||Work in progress||TBD||TBD|
|V1Employees.Timecards|| Labor API|
|V1Employees.CashDrawers|| Cash Drawers API|
|V1Items|| Catalog API|
|V1Locations|| Locations API|
|V1Transactions.Payments||pending||Work in progress||TBD||TBD|
|V1Transactions.Refunds||pending||Work in progress||TBD||TBD|
|V1Transactions.Settlements||pending||Work in progress||TBD||TBD|
|V1Transactions.BankAccounts|| Bank Accounts API|
|V2Transactions|| Payments API|
The following endpoints are deprecated and currently scheduled for retirement, but the associated APIs are still generally available. See the associated migration guide or relevant Technical Reference entry for guidance.
The following fields are retired and replaced.