connect.squareup.com · PaymentsSubscribeShare
Square API breaking changes
The breaking changes Square API announced that Okapi tracks: 6 in all.
Do you run the Square API? Make sure your users call it right →
At a glance
- API host
connect.squareup.com- Kind
- Payments
- Versions with breaking changes
- v2 (5)
- Breaking changes tracked
- 3 breaking changes with no date yet and 3 already in effect
- Last updated
Deprecated, no date yet 3
-
No date
/v2/customers/{id}/cards*Endpoint removal Deprecated, no date -
No date
/v2/labor/shifts*Endpoint removal Deprecated, no date -
No date
GET /v2/locations/{id}/transactions*Endpoint removal Deprecated, no date
Already in effect 3
-
POST /v2/locations/{id}/transactions*Endpoint removal Stopped working -
POST /mobile/authorization-codeEndpoint removal Stopped working -
POST /v2/paymentsParameter removal Stopped working
Where Okapi reads it
- Changelog developer.squareup.com/docs/changelog/connect
- OpenAPI spec raw.githubusercontent.com/square/connect-api-specification/master/api.json
- Announcement developer.squareup.com/docs/changelog/connect-logs/2025-02-20
- Announcement developer.squareup.com/docs/changelog/connect-logs/2025-08-20
- Announcement developer.squareup.com/docs/customers-api/what-it-does
- Announcement developer.squareup.com/docs/labor-api/what-it-does
- Announcement developer.squareup.com/docs/payments-api/migrate-from-transactions-api
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub