What Square changed, 16 October 2025 to 15 September 2026
327 operations became 332. 4 were removed, 0 were newly deprecated, 9 were added, and 0 request fields became required.
Read from square/connect-api-specification at 1b6956b and 79ccc3f (version 2.0). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Square's published specification.
Square publishes its API description in square/connect-api-specification. This page reads api.json from that repository. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.
Removed from the specification
- GET /v2/inventory/transfers/{transfer_id} removed in e695f01 · 14 July 2026
- POST /mobile/authorization-code removed in 164cc74 · 19 May 2026
- POST /v2/locations/{location_id}/transactions/{transaction_id}/capture removed in 79ccc3f · 15 September 2026
- POST /v2/locations/{location_id}/transactions/{transaction_id}/void removed in 79ccc3f · 15 September 2026
Newly deprecated in this window
A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.
No compared operation (one paired with a baseline operation) gained the deprecated flag in this window.
Deprecated as of the current specification (24)
Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.
- DELETE /v2/customers/{customer_id}/cards/{card_id}
- DELETE /v2/labor/shifts/{id}
- GET /v1/{location_id}/orders
- GET /v1/{location_id}/orders/{order_id}
- GET /v2/employees
- GET /v2/employees/{id}
- GET /v2/inventory/adjustment/{adjustment_id}
- GET /v2/inventory/physical-count/{physical_count_id}
- GET /v2/inventory/{catalog_object_id}/changes
- GET /v2/labor/employee-wages
- GET /v2/labor/employee-wages/{id}
- GET /v2/labor/shifts/{id}
- GET /v2/locations/{location_id}/transactions
- GET /v2/locations/{location_id}/transactions/{transaction_id}
- GET /v2/loyalty/programs
- POST /v2/customers/{customer_id}/cards
- POST /v2/inventory/batch-change
- POST /v2/inventory/batch-retrieve-changes
- POST /v2/inventory/batch-retrieve-counts
- POST /v2/labor/shifts
- POST /v2/labor/shifts/search
- POST /v2/locations/{location_id}/checkouts
- PUT /v1/{location_id}/orders/{order_id}
- PUT /v2/labor/shifts/{id}
Entries without a link were already marked deprecated at 1b6956b · 16 October 2025, the baseline compared here.
Request fields removed from the specification
The current specification no longer lists these request fields, which the baseline did. A caller that still sends one is sending a parameter the new version does not define; whether Square rejects or ignores it at runtime is not something a specification diff can show, and what it means for an integration depends on how Square versions — see the note at the top of this page.
- POST /v2/inventory/batch-change no longer lists changes[].adjustment.location_id (application/json)
- POST /v2/inventory/batch-change no longer lists changes[].transfer (application/json)
- POST /v2/inventory/changes/batch-create no longer lists changes[].adjustment.location_id (application/json)
- POST /v2/inventory/changes/batch-create no longer lists changes[].transfer (application/json)
Square API questions
Every answer below is computed from the snapshot above, and each links to the Square specification it was read from.
- Which Square API endpoints were removed recently?
- 4 operations were removed from api.json in square/connect-api-specification between 16 October 2025 and 15 September 2026: GET /v2/inventory/transfers/{transfer_id}, POST /mobile/authorization-code, POST /v2/locations/{location_id}/transactions/{transaction_id}/capture and POST /v2/locations/{location_id}/transactions/{transaction_id}/void. The file went from 327 to 332 operations.
- Source: square/connect-api-specification, the two commits compared
- Which Square API endpoints are deprecated?
- As of 15 September 2026, api.json in square/connect-api-specification marks 24 operations deprecated: DELETE /v2/customers/{customer_id}/cards/{card_id}, DELETE /v2/labor/shifts/{id}, GET /v1/{location_id}/orders, GET /v1/{location_id}/orders/{order_id}, GET /v2/employees, GET /v2/employees/{id}, GET /v2/inventory/adjustment/{adjustment_id}, GET /v2/inventory/physical-count/{physical_count_id} and 16 more (all listed above). No compared operation (one the comparison paired with a baseline operation) gained the deprecated flag between 16 October 2025 and 15 September 2026. 24 were already deprecated at the baseline.
- Source: square/connect-api-specification, the two commits compared
- Did any Square API request fields become required?
- None between 16 October 2025 and 15 September 2026, among the JSON request bodies in api.json in square/connect-api-specification the comparison could read. A field inside a union (anyOf or oneOf) is not compared, so it is not counted either way.
- Source: square/connect-api-specification, the two commits compared
- Where is the Square OpenAPI specification?
- In the square/connect-api-specification repository on GitHub. This page reads api.json at commit 79ccc3f (version 2.0), dated 15 September 2026.
- Source: square/connect-api-specification on GitHub
The Action does not check Square yet
It checks GitHub REST and Stripe. If you want your CI to check the Square endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.