docs(api): clarify simulateClearing supports multiple calls

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 214
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lithic/lithic-9e397c65ffb81e2928b8ecf979769a79131ae6058b6fb373a5e930dc8a168732.yml
-openapi_spec_hash: 93aea3855d2d1c390107d223762aa818
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lithic/lithic-1514911f233cb8bf0d6752c45bfa53a61b8f9b8ff215a4ea94a95f9505911000.yml
+openapi_spec_hash: 9820a9c9a4ff778c627041eb53fd4ee5
 config_hash: 5bb913c05ebeb301ec925b16e75bb251

lithic-java-core/src/main/kotlin/com/lithic/api/models/TransactionSimulateClearingParams.kt

@@ -23,8 +23,9 @@ import java.util.Optional
  * Clears an existing authorization, either debit or credit. After this event, the transaction
  * transitions from `PENDING` to `SETTLED` status.
  *
- * If `amount` is not set, the full amount of the transaction will be cleared. Transactions that
- * have already cleared, either partially or fully, cannot be cleared again using this endpoint.
+ * If `amount` is not set, the full amount of the transaction will be cleared. This endpoint may be
+ * called multiple times against the same authorization to simulate a multiple-completion scenario,
+ * with each call creating a separate clearing event.
  */
 class TransactionSimulateClearingParams
 private constructor(
@@ -48,8 +49,9 @@ private constructor(
      * result in a -100 amount in the transaction, if the original authorization is a credit
      * authorization.
      *
-     * If `amount` is not set, the full amount of the transaction will be cleared. Transactions that
-     * have already cleared, either partially or fully, cannot be cleared again using this endpoint.
+     * If `amount` is not set, the full amount of the transaction will be cleared. This endpoint may
+     * be called multiple times against the same authorization to simulate a multiple-completion
+     * scenario, with each call creating a separate clearing event.
      *
      * @throws LithicInvalidDataException if the JSON field has an unexpected type (e.g. if the
      *   server responded with an unexpected value).
@@ -138,9 +140,9 @@ private constructor(
          * field will result in a -100 amount in the transaction, if the original authorization is a
          * credit authorization.
          *
-         * If `amount` is not set, the full amount of the transaction will be cleared. Transactions
-         * that have already cleared, either partially or fully, cannot be cleared again using this
-         * endpoint.
+         * If `amount` is not set, the full amount of the transaction will be cleared. This endpoint
+         * may be called multiple times against the same authorization to simulate a
+         * multiple-completion scenario, with each call creating a separate clearing event.
          */
         fun amount(amount: Long) = apply { body.amount(amount) }
 
@@ -324,9 +326,9 @@ private constructor(
          * field will result in a -100 amount in the transaction, if the original authorization is a
          * credit authorization.
          *
-         * If `amount` is not set, the full amount of the transaction will be cleared. Transactions
-         * that have already cleared, either partially or fully, cannot be cleared again using this
-         * endpoint.
+         * If `amount` is not set, the full amount of the transaction will be cleared. This endpoint
+         * may be called multiple times against the same authorization to simulate a
+         * multiple-completion scenario, with each call creating a separate clearing event.
          *
          * @throws LithicInvalidDataException if the JSON field has an unexpected type (e.g. if the
          *   server responded with an unexpected value).
@@ -405,9 +407,9 @@ private constructor(
              * this field will result in a -100 amount in the transaction, if the original
              * authorization is a credit authorization.
              *
-             * If `amount` is not set, the full amount of the transaction will be cleared.
-             * Transactions that have already cleared, either partially or fully, cannot be cleared
-             * again using this endpoint.
+             * If `amount` is not set, the full amount of the transaction will be cleared. This
+             * endpoint may be called multiple times against the same authorization to simulate a
+             * multiple-completion scenario, with each call creating a separate clearing event.
              */
             fun amount(amount: Long) = amount(JsonField.of(amount))
 

lithic-java-core/src/main/kotlin/com/lithic/api/services/async/TransactionServiceAsync.kt

@@ -217,8 +217,9 @@ interface TransactionServiceAsync {
      * Clears an existing authorization, either debit or credit. After this event, the transaction
      * transitions from `PENDING` to `SETTLED` status.
      *
-     * If `amount` is not set, the full amount of the transaction will be cleared. Transactions that
-     * have already cleared, either partially or fully, cannot be cleared again using this endpoint.
+     * If `amount` is not set, the full amount of the transaction will be cleared. This endpoint may
+     * be called multiple times against the same authorization to simulate a multiple-completion
+     * scenario, with each call creating a separate clearing event.
      */
     fun simulateClearing(
         params: TransactionSimulateClearingParams

lithic-java-core/src/main/kotlin/com/lithic/api/services/blocking/TransactionService.kt

@@ -206,8 +206,9 @@ interface TransactionService {
      * Clears an existing authorization, either debit or credit. After this event, the transaction
      * transitions from `PENDING` to `SETTLED` status.
      *
-     * If `amount` is not set, the full amount of the transaction will be cleared. Transactions that
-     * have already cleared, either partially or fully, cannot be cleared again using this endpoint.
+     * If `amount` is not set, the full amount of the transaction will be cleared. This endpoint may
+     * be called multiple times against the same authorization to simulate a multiple-completion
+     * scenario, with each call creating a separate clearing event.
      */
     fun simulateClearing(
         params: TransactionSimulateClearingParams