feat(api): api update

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 139
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/orb/orb-5192a1b7cab269d33dbc3c9eb75994d41880eff1694900232b99f4cc30ae5710.yml
-openapi_spec_hash: 1bcfe26f0efab1f1287195a45074fae5
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/orb/orb-0b931ef1842e244faf237ea9dd3f8be2cadf24410a1cbb0bdae6f1f03fd1067d.yml
+openapi_spec_hash: b704b2673cb93856fd500e61301c661c
 config_hash: c01c1191b1cd696c7ca855ff6d28a8df

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

@@ -128,8 +128,8 @@ import kotlin.jvm.optionals.getOrNull
  * all usage is billed for in the corresponding billing period.
  *
  * In general, Orb does not expect events with future dated timestamps. In cases where the timestamp
- * is at least 24 hours ahead of the current time, the event will not be accepted as a valid event,
- * and will throw validation errors.
+ * is 5 minutes ahead of the current time, the event will not be accepted as a valid event, and will
+ * throw validation errors.
  *
  * ## Event validation
  *
@@ -142,7 +142,7 @@ import kotlin.jvm.optionals.getOrNull
  * - If the `external_customer_id` is specified, the customer in Orb does not need to exist. Events
  *   will be attributed to any future customers with the `external_customer_id` on subscription
  *   creation.
- * - `timestamp` must conform to ISO 8601 and represent a timestamp at most 1 hour in the future.
+ * - `timestamp` must conform to ISO 8601 and represent a timestamp at most 5 minutes in the future.
  *   This timestamp should be sent in UTC timezone (no timezone offset).
  *
  * ## Idempotency and retry semantics

orb-java-core/src/main/kotlin/com/withorb/api/services/async/EventServiceAsync.kt

@@ -289,8 +289,8 @@ interface EventServiceAsync {
      * and ensure that all usage is billed for in the corresponding billing period.
      *
      * In general, Orb does not expect events with future dated timestamps. In cases where the
-     * timestamp is at least 24 hours ahead of the current time, the event will not be accepted as a
-     * valid event, and will throw validation errors.
+     * timestamp is 5 minutes ahead of the current time, the event will not be accepted as a valid
+     * event, and will throw validation errors.
      *
      * ## Event validation
      *
@@ -303,7 +303,7 @@ interface EventServiceAsync {
      * - If the `external_customer_id` is specified, the customer in Orb does not need to exist.
      *   Events will be attributed to any future customers with the `external_customer_id` on
      *   subscription creation.
-     * - `timestamp` must conform to ISO 8601 and represent a timestamp at most 1 hour in the
+     * - `timestamp` must conform to ISO 8601 and represent a timestamp at most 5 minutes in the
      *   future. This timestamp should be sent in UTC timezone (no timezone offset).
      *
      * ## Idempotency and retry semantics

orb-java-core/src/main/kotlin/com/withorb/api/services/blocking/EventService.kt

@@ -285,8 +285,8 @@ interface EventService {
      * and ensure that all usage is billed for in the corresponding billing period.
      *
      * In general, Orb does not expect events with future dated timestamps. In cases where the
-     * timestamp is at least 24 hours ahead of the current time, the event will not be accepted as a
-     * valid event, and will throw validation errors.
+     * timestamp is 5 minutes ahead of the current time, the event will not be accepted as a valid
+     * event, and will throw validation errors.
      *
      * ## Event validation
      *
@@ -299,7 +299,7 @@ interface EventService {
      * - If the `external_customer_id` is specified, the customer in Orb does not need to exist.
      *   Events will be attributed to any future customers with the `external_customer_id` on
      *   subscription creation.
-     * - `timestamp` must conform to ISO 8601 and represent a timestamp at most 1 hour in the
+     * - `timestamp` must conform to ISO 8601 and represent a timestamp at most 5 minutes in the
      *   future. This timestamp should be sent in UTC timezone (no timezone offset).
      *
      * ## Idempotency and retry semantics