GET /v2/locations/{}/transactions* → endpoint removal
Squareupsandbox
Deprecated, no date
Squareupsandbox deprecated GET /v2/locations/{}/transactions* without giving a shutdown date yet.
Calls it hits
GET /v2/locations/{}/transactions*
What to use instead of these calls
Read payments with GET /v2/payments and GET /v2/payments/{payment_id}, and refunds with GET /v2/refunds.
In Squareupsandbox's words
The Transactions API is deprecated. As of September 16, 2026, its write operations ( Charge, CreateRefund, CaptureTransaction, and VoidTransaction) are retired. Use the Payments API and Refunds API for new payment processing and refunds. Read operations remain available for historical transaction data.
Facts
- API
- Squareupsandbox
connect.squareupsandbox.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Squareupsandbox's own pages
Questions
When does this change take effect?
Squareupsandbox deprecated GET /v2/locations/{}/transactions* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Squareupsandbox has not given a shutdown date yet.
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 Squareupsandbox 5
-
POST /v2/paymentsEndpoint removal Stopped working -
POST /mobile/authorization-codeEndpoint removal Stopped working -
POST /v2/locations/{}/transactions*Endpoint removal Stopped working -
No date
/v2/customers/{}/cards*Endpoint removal Deprecated, no date -
No date
/v2/labor/shifts*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.