Square breaking change: POST /v2/locations/{location_id}/transactions/{transaction_id}/capture
api path removed with deprecation
Specification capture: . Published evidence last updated . This is captured contract evidence, not an observed outage or a result from scanning your code.
Which field and classification rule changed?
- Changed field
Operation-level change- Rule ID
operation.endpoint_removed- Classifier version
2026-10-15.2- Direction
- operation
- Finding ID
chg_24493c5697185eb224aa3f388c25d1579728c7a020dca52f79573f1f638eb830
What is the recorded before and after evidence?
Previous specification SHA-256: cb96e87d7789bbf44e7623e427fb404612f90eb2e31d86b323642414e3372aed
Revised specification SHA-256: baf3257b697086449c4026d5ebf57a2f2fa668556ddfb8cbca261fde4dc82135
Publisher version: 2.0 to 2.0.
- post:
- deprecated: true
- description: |-
- Captures a transaction that was created with the [Charge](api-endpoint:Transactions-Charge)
- endpoint with a `delay_capture` value of `true`.
-
-
- See [Delayed capture transactions](https://developer.squareup.com/docs/payments/transactions/overview#delayed-capture)
- for more information.
- operationId: CaptureTransaction
- parameters:
- - description: ""
- in: path
- name: location_id
- required: true
- schema:
- type: string
- - description: ""
- in: path
- name: transaction_id
- required: true
- schema:
- type: string
- responses:
- "200":
- content:
- application/json:
- schema:
- description: >-
- Defines the fields that are included in the response body of
-
- a request to the
- [CaptureTransaction](api-endpoint:Transactions-CaptureTransaction)
- endpoint.
- example: {}
- properties:
- errors:
- description: Any errors that occurred during the request.
- items:
- description: |-Inspect the complete release · Public source findings · Publisher specification source
How do I check whether this affects my code?
Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.
Check an authorized repository · Review coverage · Inspect classification rules