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

lib/orb/resources/customers/credits/ledger.rb

@@ -33,11 +33,9 @@ class Ledger
           #
           # 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.
+          # result in a ledger 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
@@ -486,11 +484,9 @@ def create_entry_by_external_id(external_customer_id, params)
           #
           # 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.
+          # result in a ledger 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

rbi/orb/resources/customers/credits/ledger.rbi

@@ -30,11 +30,9 @@ module Orb
           #
           # 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.
+          # result in a ledger 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
@@ -533,11 +531,9 @@ module Orb
           #
           # 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.
+          # result in a ledger 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