Okapi Okapi

Square API GET /v2/locations/{id}/transactions* endpoint removal

Deprecated, no dateSubscribe to Square APIShare

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.


Calls it hits

  • GET /v2/locations/{id}/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 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.

Square API, Announcement

Facts

API
Square API connect.squareup.com
Kind
Endpoint removal
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Square API's own pages

Questions

When does this change take effect?

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

Do these calls still work?

Yes, they still work: Square API 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 Square API 5

  1. POST /v2/paymentsParameter removal Stopped working
  2. POST /mobile/authorization-codeEndpoint removal Stopped working
  3. POST /v2/locations/{id}/transactions*Endpoint removal Stopped working
  4. No date /v2/customers/{id}/cards*Endpoint removal Deprecated, no date
  5. 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.

Add to GitHub

Get notifications

Subscribe to Square API

Hear about each breaking change Square API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Square API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.