feat(api): api update

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 126
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/orb%2Forb-c131de17773b450eb1ec03ca001f94d3777e35347234869a7efee083003e1513.yml
-openapi_spec_hash: 5d2d4a3a9ada1c381efb318b6897994d
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/orb%2Forb-6017828d1287c194d4d7759dc5b5410225ab58af66ff8605315f70f5e623b82d.yml
+openapi_spec_hash: 4390eaf377258fcd7db1dbc073a2c23f
 config_hash: bcf82bddb691f6be773ac6cae8c03b9a

orb-java-core/src/main/kotlin/com/withorb/api/models/CustomerCreditLedgerListByExternalIdParams.kt

@@ -38,10 +38,8 @@ import kotlin.jvm.optionals.getOrNull
  *
  * As usage for a customer is reported into Orb, credits may be deducted according to the customer's
  * plan configuration. An automated deduction of this type will result in a ledger entry, also with
- * a starting and ending balance. In order to provide better tracing capabilities for automatic
- * deductions, Orb always associates each automatic deduction with the `event_id` at the time of
- * ingestion, used to pinpoint _why_ credit deduction took place and to ensure that credits are
- * never deducted without an associated usage event.
+ * a starting and ending balance. Each day's usage for a particular price, invoice, and block will
+ * be grouped into a single entry.
  *
  * By default, Orb uses an algorithm that automatically deducts from the *soonest expiring credit
  * block* first in order to ensure that all credits are utilized appropriately. As an example, if

orb-java-core/src/main/kotlin/com/withorb/api/models/CustomerCreditLedgerListParams.kt

@@ -38,10 +38,8 @@ import kotlin.jvm.optionals.getOrNull
  *
  * As usage for a customer is reported into Orb, credits may be deducted according to the customer's
  * plan configuration. An automated deduction of this type will result in a ledger entry, also with
- * a starting and ending balance. In order to provide better tracing capabilities for automatic
- * deductions, Orb always associates each automatic deduction with the `event_id` at the time of
- * ingestion, used to pinpoint _why_ credit deduction took place and to ensure that credits are
- * never deducted without an associated usage event.
+ * a starting and ending balance. Each day's usage for a particular price, invoice, and block will
+ * be grouped into a single entry.
  *
  * By default, Orb uses an algorithm that automatically deducts from the *soonest expiring credit
  * block* first in order to ensure that all credits are utilized appropriately. As an example, if

orb-java-core/src/main/kotlin/com/withorb/api/services/async/customers/credits/LedgerServiceAsync.kt

@@ -54,10 +54,8 @@ interface LedgerServiceAsync {
      *
      * As usage for a customer is reported into Orb, credits may be deducted according to the
      * customer's plan configuration. An automated deduction of this type will result in a ledger
-     * entry, also with a starting and ending balance. In order to provide better tracing
-     * capabilities for automatic deductions, Orb always associates each automatic deduction with
-     * the `event_id` at the time of ingestion, used to pinpoint _why_ credit deduction took place
-     * and to ensure that credits are never deducted without an associated usage event.
+     * entry, also with a starting and ending balance. Each day's usage for a particular price,
+     * invoice, and block will be grouped into a single entry.
      *
      * By default, Orb uses an algorithm that automatically deducts from the *soonest expiring
      * credit block* first in order to ensure that all credits are utilized appropriately. As an
@@ -415,10 +413,8 @@ interface LedgerServiceAsync {
      *
      * As usage for a customer is reported into Orb, credits may be deducted according to the
      * customer's plan configuration. An automated deduction of this type will result in a ledger
-     * entry, also with a starting and ending balance. In order to provide better tracing
-     * capabilities for automatic deductions, Orb always associates each automatic deduction with
-     * the `event_id` at the time of ingestion, used to pinpoint _why_ credit deduction took place
-     * and to ensure that credits are never deducted without an associated usage event.
+     * entry, also with a starting and ending balance. Each day's usage for a particular price,
+     * invoice, and block will be grouped into a single entry.
      *
      * By default, Orb uses an algorithm that automatically deducts from the *soonest expiring
      * credit block* first in order to ensure that all credits are utilized appropriately. As an

orb-java-core/src/main/kotlin/com/withorb/api/services/blocking/customers/credits/LedgerService.kt

@@ -54,10 +54,8 @@ interface LedgerService {
      *
      * As usage for a customer is reported into Orb, credits may be deducted according to the
      * customer's plan configuration. An automated deduction of this type will result in a ledger
-     * entry, also with a starting and ending balance. In order to provide better tracing
-     * capabilities for automatic deductions, Orb always associates each automatic deduction with
-     * the `event_id` at the time of ingestion, used to pinpoint _why_ credit deduction took place
-     * and to ensure that credits are never deducted without an associated usage event.
+     * entry, also with a starting and ending balance. Each day's usage for a particular price,
+     * invoice, and block will be grouped into a single entry.
      *
      * By default, Orb uses an algorithm that automatically deducts from the *soonest expiring
      * credit block* first in order to ensure that all credits are utilized appropriately. As an
@@ -409,10 +407,8 @@ interface LedgerService {
      *
      * As usage for a customer is reported into Orb, credits may be deducted according to the
      * customer's plan configuration. An automated deduction of this type will result in a ledger
-     * entry, also with a starting and ending balance. In order to provide better tracing
-     * capabilities for automatic deductions, Orb always associates each automatic deduction with
-     * the `event_id` at the time of ingestion, used to pinpoint _why_ credit deduction took place
-     * and to ensure that credits are never deducted without an associated usage event.
+     * entry, also with a starting and ending balance. Each day's usage for a particular price,
+     * invoice, and block will be grouped into a single entry.
      *
      * By default, Orb uses an algorithm that automatically deducts from the *soonest expiring
      * credit block* first in order to ensure that all credits are utilized appropriately. As an