timelogic-api 1.0.3 → 2.0.0

data/lib/timelogic-api/api/utility_api.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/api_client.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -309,6 +309,8 @@ module TimeLogic::Api
       Array(auth_names).each do |auth_name|
         auth_setting = @config.auth_settings[auth_name]
         next unless auth_setting
+        value = auth_setting[:value].to_s.strip
+        next if value.empty? || value == 'Bearer'
         case auth_setting[:in]
         when 'header' then header_params[auth_setting[:key]] = auth_setting[:value]
         when 'query'  then query_params[auth_setting[:key]] = auth_setting[:value]

data/lib/timelogic-api/api_error.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/configuration.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/models/api_error.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/models/bulk_error.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -20,7 +20,7 @@ module TimeLogic::Api
 
     attr_accessor :request_id
 
-    # Intentionally omitted from public API error responses to avoid exposing request timing; use request_id for support correlation.
+    # Intentionally omitted from public API error responses, including per-item errors inside bulk arrays, to avoid exposing request timing; use request_id for support correlation.
     attr_accessor :timestamp
 
     attr_accessor :item

data/lib/timelogic-api/models/calendar_response.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -27,6 +27,7 @@ module TimeLogic::Api
 
     attr_accessor :human
 
+    # Day of the week counted from Sunday (1 = Sunday, 2 = Monday ... 7 = Saturday).
     attr_accessor :day_number
 
     attr_accessor :day_short
@@ -45,6 +46,7 @@ module TimeLogic::Api
 
     attr_accessor :day
 
+    # ISO 8601 week number (present with `week=true`). It belongs to the ISO week-year, which is not returned and can differ from `year` near January 1 (2027-01-01 is week 53 of 2026).
     attr_accessor :week_number
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/timelogic-api/models/diff_endpoint_ref.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/models/diff_response.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/models/dst_response.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -27,6 +27,7 @@ module TimeLogic::Api
 
     attr_accessor :human
 
+    # Day of the week counted from Sunday (1 = Sunday, 2 = Monday ... 7 = Saturday).
     attr_accessor :day_number
 
     attr_accessor :day_short
@@ -39,6 +40,7 @@ module TimeLogic::Api
 
     attr_accessor :dst_active
 
+    # Present only with `next=true`. The instant of the next UTC offset change, written in the offset in force before it (e.g. `2026-11-01T02:00:00-04:00`); the new offset is not returned. `null` when no change is scheduled, for offset targets and with no selector. Tracks offset changes only, so `dst_active` can change without one.
     attr_accessor :next_transition
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/timelogic-api/models/elapsed_response.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -25,7 +25,7 @@ module TimeLogic::Api
 
     attr_accessor :human
 
-    # `left` means the target instant is still in the future. `passed` means the target instant is already in the past.
+    # `left` means the reference instant is after the compared instant (now, or `compare_*`). `passed` means it is before it, or equal to it.
     attr_accessor :direction
 
     attr_accessor :formatted

data/lib/timelogic-api/models/error_response.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -19,7 +19,7 @@ module TimeLogic::Api
 
     attr_accessor :request_id
 
-    # Intentionally omitted from public API error responses to avoid exposing request timing; use request_id for support correlation.
+    # Intentionally omitted from public API error responses, including per-item errors inside bulk arrays, to avoid exposing request timing; use request_id for support correlation.
     attr_accessor :timestamp
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/timelogic-api/models/get_current_time200_response.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/models/jwk_key.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -27,6 +27,12 @@ module TimeLogic::Api
 
     attr_accessor :x
 
+    # Permitted key operations; published keys allow only `verify`.
+    attr_accessor :key_ops
+
+    # JWK extractable flag as exported by the signing worker; always `true`.
+    attr_accessor :ext
+
     class EnumAttributeValidator
       attr_reader :datatype
       attr_reader :allowable_values
@@ -57,7 +63,9 @@ module TimeLogic::Api
         :'alg' => :'alg',
         :'use' => :'use',
         :'kid' => :'kid',
-        :'x' => :'x'
+        :'x' => :'x',
+        :'key_ops' => :'key_ops',
+        :'ext' => :'ext'
       }
     end
 
@@ -74,7 +82,9 @@ module TimeLogic::Api
         :'alg' => :'String',
         :'use' => :'String',
         :'kid' => :'String',
-        :'x' => :'String'
+        :'x' => :'String',
+        :'key_ops' => :'Array<String>',
+        :'ext' => :'Boolean'
       }
     end
 
@@ -134,6 +144,16 @@ module TimeLogic::Api
       else
         self.x = nil
       end
+
+      if attributes.key?(:'key_ops')
+        if (value = attributes[:'key_ops']).is_a?(Array)
+          self.key_ops = value
+        end
+      end
+
+      if attributes.key?(:'ext')
+        self.ext = attributes[:'ext']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -239,7 +259,9 @@ module TimeLogic::Api
           alg == o.alg &&
           use == o.use &&
           kid == o.kid &&
-          x == o.x
+          x == o.x &&
+          key_ops == o.key_ops &&
+          ext == o.ext
     end
 
     # @see the `==` method
@@ -251,7 +273,7 @@ module TimeLogic::Api
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [kty, crv, alg, use, kid, x].hash
+      [kty, crv, alg, use, kid, x, key_ops, ext].hash
     end
 
     # Builds the object from hash

data/lib/timelogic-api/models/jwks_response.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/models/time_payload.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -28,6 +28,7 @@ module TimeLogic::Api
 
     attr_accessor :human
 
+    # Day of the week counted from Sunday (1 = Sunday, 2 = Monday ... 7 = Saturday).
     attr_accessor :day_number
 
     attr_accessor :day_short

data/lib/timelogic-api/models/time_payload_bulk_item.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/timelogic-api/models/time_payload_bulk_response.rb

@@ -1,7 +1,7 @@
 =begin
 #TimeLogic API | A World Time API
 
-# Official public API contract for TimeLogic API.
+#Direct API contract for client integrations. It documents authentication, endpoint parameters, response shapes, public signing keys, and signed JSON controls.  Authentication: - the API supports `Authorization: Bearer <token>`, `X-API-Key`, and `api_key` query credentials - RapidAPI access uses `X-RapidAPI-Key` and `X-RapidAPI-Host`; the SDKs expose this as a `rapidApi` transport option that accepts only the RapidAPI key  Behavioral notes: - all documented operations are `GET` - only one selector family may be used at a time - current and convert support bulk only through one comma-separated `tz`, `ip`, or `offset` selector - bulk selectors accept at most 10 values, and every request URL is limited to 8192 characters - add, diff, calendar, dst, elapsed, timezone, and clock are single-target routes - credentials are extracted in Authorization, X-API-Key, then api_key query order; conflicting values are rejected - the first server is the default API host. The second server is the RapidAPI gateway and can be selected or overridden by SDK configuration - `sign` is available on supported JSON routes and is not supported on `/v1/time/clock`
 
 The version of the OpenAPI document: 1.0.0
 
@@ -10,201 +10,47 @@ Generator version: 7.10.0
 
 =end
 
-require 'date'
-require 'time'
-
 module TimeLogic::Api
-  # Bulk response array returned when `/v1/time/current` or `/v1/time/convert` receives one comma-separated `tz`, `ip`, or `offset` selector.
+  # Bulk response array returned when `/v1/time/current` or `/v1/time/convert`
+  # receives one comma-separated `tz`, `ip`, or `offset` selector. Each item is
+  # a TimePayload or, for a selector that failed, a BulkError, in request order.
   class TimePayloadBulkResponse < Array
-    # Attribute mapping from ruby-style variable name to JSON key.
-    def self.attribute_map
-      {
-      }
-    end
-
-    # Returns all the JSON keys this model knows about, including the ones defined in its parent(s)
-    def self.acceptable_attributes
-      attribute_map.values.concat(superclass.acceptable_attributes)
-    end
-
-    # Attribute type mapping.
-    def self.openapi_types
-      {
-      }
-    end
-
-    # List of attributes with nullable: true
-    def self.openapi_nullable
-      Set.new([
-      ])
-    end
-
-    # Initializes the object
-    # @param [Hash] attributes Model attributes in the form of hash
-    def initialize(attributes = {})
-      if (!attributes.is_a?(Hash))
-        fail ArgumentError, "The input argument (attributes) must be a hash in `TimeLogic::Api::TimePayloadBulkResponse` initialize method"
+    # The oneOf caster calls build for models that answer openapi_one_of.
+    # This model is not a oneOf itself; it answers so its items are cast.
+    def self.openapi_one_of
+      [:TimePayloadBulkItem]
+    end
+
+    # Builds the bulk array from parsed JSON, or returns nil for anything else.
+    # @param [Array] data Parsed JSON array
+    # @return [TimePayloadBulkResponse, nil]
+    def self.build(data)
+      return nil unless data.is_a?(Array)
+      items = data.map do |item|
+        TimePayloadBulkItem.build(item) || fail(ArgumentError, "#{item} is neither a TimePayload nor a BulkError")
       end
-
-      # check to see if the attribute exists and convert string to symbol for hash key
-      attributes = attributes.each_with_object({}) { |(k, v), h|
-        if (!self.class.attribute_map.key?(k.to_sym))
-          fail ArgumentError, "`#{k}` is not a valid attribute in `TimeLogic::Api::TimePayloadBulkResponse`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
-        end
-        h[k.to_sym] = v
-      }
-
-      # call parent's initialize
-      super(attributes)
-    end
-
-    # Show invalid properties with the reasons. Usually used together with valid?
-    # @return Array for valid properties with the reasons
-    def list_invalid_properties
-      warn '[DEPRECATED] the `list_invalid_properties` method is obsolete'
-      invalid_properties = super
-      invalid_properties
-    end
-
-    # Check to see if the all the properties in the model are valid
-    # @return true if the model is valid
-    def valid?
-      warn '[DEPRECATED] the `valid?` method is obsolete'
-      true && super
-    end
-
-    # Checks equality by comparing each attribute.
-    # @param [Object] Object to be compared
-    def ==(o)
-      return true if self.equal?(o)
-      self.class == o.class && super(o)
+      new(items)
     end
 
-    # @see the `==` method
-    # @param [Object] Object to be compared
-    def eql?(o)
-      self == o
+    # @see build
+    def self.build_from_hash(data)
+      build(data)
     end
 
-    # Calculates hash code according to all attributes.
-    # @return [Integer] Hash code
-    def hash
-      [].hash
+    # True when the item is a per-item error.
+    def self.bulk_error?(item)
+      item.is_a?(BulkError)
     end
 
-    # Builds the object from hash
-    # @param [Hash] attributes Model attributes in the form of hash
-    # @return [Object] Returns the model itself
-    def self.build_from_hash(attributes)
-      return nil unless attributes.is_a?(Hash)
-      super(attributes)
-      attributes = attributes.transform_keys(&:to_sym)
-      transformed_hash = {}
-      openapi_types.each_pair do |key, type|
-        if attributes.key?(attribute_map[key]) && attributes[attribute_map[key]].nil?
-          transformed_hash["#{key}"] = nil
-        elsif type =~ /\AArray<(.*)>/i
-          # check to ensure the input is an array given that the attribute
-          # is documented as an array but the input is not
-          if attributes[attribute_map[key]].is_a?(Array)
-            transformed_hash["#{key}"] = attributes[attribute_map[key]].map { |v| _deserialize($1, v) }
-          end
-        elsif !attributes[attribute_map[key]].nil?
-          transformed_hash["#{key}"] = _deserialize(type, attributes[attribute_map[key]])
-        end
-      end
-      new(transformed_hash)
-    end
-
-    # Deserializes the data based on type
-    # @param string type Data type
-    # @param string value Value to be deserialized
-    # @return [Object] Deserialized data
-    def self._deserialize(type, value)
-      case type.to_sym
-      when :Time
-        Time.parse(value)
-      when :Date
-        Date.parse(value)
-      when :String
-        value.to_s
-      when :Integer
-        value.to_i
-      when :Float
-        value.to_f
-      when :Boolean
-        if value.to_s =~ /\A(true|t|yes|y|1)\z/i
-          true
-        else
-          false
-        end
-      when :Object
-        # generic object (usually a Hash), return directly
-        value
-      when /\AArray<(?<inner_type>.+)>\z/
-        inner_type = Regexp.last_match[:inner_type]
-        value.map { |v| _deserialize(inner_type, v) }
-      when /\AHash<(?<k_type>.+?), (?<v_type>.+)>\z/
-        k_type = Regexp.last_match[:k_type]
-        v_type = Regexp.last_match[:v_type]
-        {}.tap do |hash|
-          value.each do |k, v|
-            hash[_deserialize(k_type, k)] = _deserialize(v_type, v)
-          end
-        end
-      else # model
-        # models (e.g. Pet) or oneOf
-        klass = TimeLogic::Api.const_get(type)
-        klass.respond_to?(:openapi_any_of) || klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value)
-      end
+    # Returns the items as plain hashes, in the API's JSON shape.
+    # @return [Array<Hash>]
+    def to_hash
+      map { |item| item.respond_to?(:to_hash) ? item.to_hash : item }
     end
+    alias to_body to_hash
 
-    # Returns the string representation of the object
-    # @return [String] String presentation of the object
     def to_s
       to_hash.to_s
     end
-
-    # to_body is an alias to to_hash (backward compatibility)
-    # @return [Hash] Returns the object in the form of hash
-    def to_body
-      to_hash
-    end
-
-    # Returns the object in the form of hash
-    # @return [Hash] Returns the object in the form of hash
-    def to_hash
-      hash = super
-      self.class.attribute_map.each_pair do |attr, param|
-        value = self.send(attr)
-        if value.nil?
-          is_nullable = self.class.openapi_nullable.include?(attr)
-          next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
-        end
-
-        hash[param] = _to_hash(value)
-      end
-      hash
-    end
-
-    # Outputs non-array value in the form of hash
-    # For object, use to_hash. Otherwise, just return the value
-    # @param [Object] value Any valid value
-    # @return [Hash] Returns the value in the form of hash
-    def _to_hash(value)
-      if value.is_a?(Array)
-        value.compact.map { |v| _to_hash(v) }
-      elsif value.is_a?(Hash)
-        {}.tap do |hash|
-          value.each { |k, v| hash[k] = _to_hash(v) }
-        end
-      elsif value.respond_to? :to_hash
-        value.to_hash
-      else
-        value
-      end
-    end
-
   end
-
 end