Square API Lifecycle
This topic outlines the lifecycle for Square APIs and establishes expectations for the various stages of development.
On this page
Square currently supports two API sets:
Connect v1 APIs. The original API set released in 2014, which is 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 might 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 (such as, new core functionality and new APIs) are also covered in the Documentation section of the Developer resource site.
General Availability (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 section of the Developer resource site.
Deprecated functionality remains publicly available but its 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.
You are strongly encouraged to migrate existing users to the applicable replacements as soon as possible to avoid disrupting their users. Developers using Square SDKs release on, or after, the deprecation date 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 about retired functionality is removed from the Technical Reference and Documentation sections of the Developer resource site. Retired functionality might 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 dates listed in the following table. For more information, see the associated migration guide.
|V1 Employees.Employees|| Team API|
|V1 Employees.EmployeeRoles|| Team API|
|V1 Employees.Timecards|| Labor API|
|V1 Employees.CashDrawers|| Cash Drawers API|
|V1Items|| Catalog API|
|V1 Locations|| Locations API|
|V1 Transactions.Payments||pending||Work in progress||TBD||TBD|
|V1 Transactions.Refunds||pending||Work in progress||TBD||TBD|
|V1 Transactions.Settlements||pending||Work in progress||TBD||TBD|
|V1 Transactions.BankAccounts|| Bank Accounts API|
|V2 Employees|| Team API|
|V2 Transactions|| Payments API|
|V2 Reporting|| Payments API|
The following endpoints are deprecated and currently scheduled for retirement, but the associated APIs are still generally available. For more information, see the associated migration guide or relevant Technical Reference entry.
The following fields are deprecated and replaced: