# GET /v2/locations/{}/transactions is deprecated

Square API deprecated GET /v2/locations/{id}/transactions* without giving a shutdown date yet.

Square has deprecated GET /v2/locations/{id}/transactions* without a shutdown date. Square API retired write operations on September 16, 2026, but read operations remain available for historical transaction data. Any affected requests that are eventually shut down will fail.

## What to use instead

Read payments with GET /v2/payments and GET /v2/payments/{payment_id}, and refunds with GET /v2/refunds.

- API: Square API (connect.squareup.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `GET /v2/locations/{id}/transactions*`
- Source: [Announcement](https://developer.squareup.com/docs/payments-api/migrate-from-transactions-api)
- Verified: November 6, 2026, against Square API's own pages
- Page: https://www.okapi.bot/providers/square-api/breaking-changes/get-v2-locations-transactions-is-deprecated/

## Square API'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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent