Square API
POST /v2/locations/{id}/transactions* endpoint removal
Stopped workingSubscribe to Square APIShare
Calls to POST /v2/locations/{id}/transactions* fail since September 16, 2026. Square API retired the write operations of the Transactions API on that day, causing requests to those endpoints to stop working.
Calls it hits
POST /v2/locations/{id}/transactions*
What to use instead of these calls
Charge with POST /v2/payments (CreatePayment), refund with POST /v2/refunds, and for delayed capture use POST /v2/payments/{payment_id}/complete or /cancel.
In Square API's words
The Transactions API is deprecated. As of September 16, 2026, its write operations ( Charge, CreateRefund, CaptureTransaction, and VoidTransaction) are retired.
Facts
- API
- Square API
connect.squareup.com - Kind
- Endpoint removal
- Takes effect
- September 16, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Square API's own pages
Questions
When does this change take effect?
Calls to POST /v2/locations/{id}/transactions* on Square API stopped working on September 16, 2026.
What happens to calls after September 16, 2026?
They have failed since September 16, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Square API 5
-
POST /v2/paymentsParameter removal Stopped working -
POST /mobile/authorization-codeEndpoint removal Stopped working -
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
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.