Connect v1 Retirement
This document provides general information about the Connect v1 retirement effort and links to migration guides for specific v1 APIs.
|V1Employees.Employees||pending||Work in progress||TBD||TBD|
|V1Employees.EmployeeRoles||pending||Work in progress||TBD||TBD|
|V1Employees.Timecards||pending||Work in progress||TBD||TBD|
|V1Employees.CashDrawers||pending||Work in progress||TBD||TBD|
|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||pending||Work in progress||TBD||TBD|
The Connect v1 APIs were introduced in 2014. Since then, Square has collected developer feedback and learned more about building robust APIs. The result is an improved Square API data model (previously known as Connect v2) that supports versioning, lays the foundation for a unified development platform, and establishes scalable patterns for future functionality.
Retiring the Connect v1 APIs will allow Square to expand interoperability with first- and third-party products, implement consistent versioning policies, and support regular iteration on functionality in response to developer feedback.
As gaps between the Square API model and Connect v1 are filled, the corresponding Connect v1 APIs will be deprecated. Square strongly recommends against using Connect v1 APIs for new applications. Deprecated endpoints are clearly flagged in the Technical Reference and Square will provide migration guides for affected developers.
Some Connect v1 functionality will not be implemented in Connect v2 due to low usage. Where possible, the applicable migration guide provides an alternative approach.
Short-term, only developers currently using a deprecated endpoint need to take immediate action. Long-term, anyone using REST or Square SDKs to call the the Connect v1 endpoints listed below will need to update their code as the retirement effort continues.
Connect v1 APIs are deprecating as their replacements become publicly available. Once a given API is deprecated, existing users will have 12 months to update their code before the functionality is retired and permanently disabled. For more information about how Square handles API deprecation and retirement, see the Square API Lifecycle overview.
Your code will break.
Retired functionality cannot be used, regardless of the
Square-Version provided during the API call. Square SDKs released on or after the retirement date do not include retired features and REST calls that attempt to use retired functionality return errors.