This topic lists the APIs in the Square Developer Platform that are deprecated and scheduled for retirement. For information about the path from API deprecation to retirement, see Square API Lifecycle.
Migrate from Deprecated APIs
The following Square APIs and Connect v1 APIs are deprecated and scheduled for retirement or recently retired and no longer supported. For general information that applies when migrating from Connect v1 APIs to Square APIs, see General Guidance for Migrating from Connect v1 APIs. For detailed guidance about migrating your code to use the replacement Square API, refer to the migration guide provided in the table for the deprecated API.
The following Square APIs are deprecated.
API | Replacement | Deprecation | Retirement |
---|---|---|---|
Employees | Team API Migration guide | 2020-08-26 | 2021-08-26 |
Transactions | Payments API Migration guide | 2019-08-15 | TBD |
The following Connect v1 APIs are retired.
API | Replacement | Deprecation | Retirement |
---|---|---|---|
Transactions.Payments | Payments API Migration guide | 2021-05-13 | 2023-06-20 |
Transactions.Refunds | Refunds API Migration guide | 2021-05-13 | 2023-06-20 |
Transactions.Settlements | Payouts API Migration guide | 2022-04-20 | 2023-06-20 |
Note
The preceding tables list API sets that are deprecated or retired. The Square Development Platform also includes deprecated endpoints and deprecated objects, fields, enums, and values.
If you have questions or need help migrating from deprecated APIs, contact Developer Support, join our Discord community, or reach out to your Square account manager.
Your code will break.
Retired functionality cannot be used, regardless of the Square-Version
provided during the API call. REST calls that attempt to use retired functionality return errors. Square SDKs released on or after retirement don't include retired features.