Square API
/v2/labor/shifts* endpoint removal
Deprecated, no dateSubscribe to Square APIShare
Square has deprecated the /v2/labor/shifts* endpoints without providing a shutdown date. This deprecation affects all Shift endpoints under that path, which are intended to eventually fail once retired. Square notes that Shift endpoints are replaced by Timecard endpoints that provide the same functionality.
Calls it hits
/v2/labor/shifts*
What to use instead of these calls
Use the Timecard endpoints under /v2/labor/timecards instead, including CreateTimecard, SearchTimecards, RetrieveTimecard, UpdateTimecard, and DeleteTimecard.
In Square API's words
all Shift endpoints ( /v2/labor/shifts/...) are replaced by Timecard endpoints ( /v2/labor/timecards/...) that provide the same functionality.
Facts
- API
- Square API
connect.squareup.com - Kind
- Endpoint removal
- Announced
- May 21, 2025
- 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 /v2/labor/shifts* 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
-
POST /v2/paymentsParameter removal Stopped working -
POST /mobile/authorization-codeEndpoint removal Stopped working -
POST /v2/locations/{id}/transactions*Endpoint removal Stopped working -
No date
/v2/customers/{id}/cards*Endpoint removal Deprecated, no date -
No date
GET /v2/locations/{id}/transactions*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.