timelogic-api 1.0.3 → 1.1.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/get_timezone200_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
 

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
 

data/lib/timelogic-api/models/timezone_match.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

data/lib/timelogic-api/models/timezone_offset_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
 
@@ -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
@@ -42,6 +43,7 @@ module TimeLogic::Api
 
     attr_accessor :dst
 
+    # For `offset=` lookups, the geographic zones whose current offset equals the requested one. `UTC` and `Etc/*` zones are intentionally excluded; use `tz=UTC` for UTC.
     attr_accessor :matching_zones
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/timelogic-api/models/timezone_resolved_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
 
@@ -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/version.rb

@@ -2,6 +2,6 @@
 
 module TimeLogic
   module Api
-    VERSION = '1.0.3'
+    VERSION = '1.1.0'
   end
 end

data/lib/timelogic-api/world_time_api.rb

@@ -0,0 +1,192 @@
+# frozen_string_literal: true
+
+# WorldTimeAPI-compatible client for the TimeLogic API /api/* routes.
+#
+# Contract: openapi/openapi-worldtimeapi.yaml. The routes answer the same paths, field
+# names and plain-text variants as worldtimeapi.org; a TimeLogic API key is required and
+# is sent as the X-API-Key header. This module uses Ruby's standard library only and does
+# not use or change the generated /v1 ApiClient, Configuration or TransportConfiguration.
+#
+#   client = TimeLogic::Api::WorldTimeApi::Client.new(api_key: ENV.fetch('TIMELOGIC_API_KEY'))
+#   now = client.get_timezone('Europe/London')
+#   puts now.datetime
+
+require 'json'
+require 'net/http'
+require 'uri'
+
+module TimeLogic
+  module Api
+    module WorldTimeApi
+      DEFAULT_BASE_URL = 'https://api.timelogicapi.com'
+
+      FIELDS = %i[
+        abbreviation client_ip datetime day_of_week day_of_year dst dst_from dst_offset
+        dst_until raw_offset timezone unixtime utc_datetime utc_offset week_number
+      ].freeze
+
+      # Time object with the worldtimeapi.org field names and types.
+      DateTime = Struct.new(*FIELDS, keyword_init: true) do
+        def self.from_hash(hash)
+          new(**FIELDS.to_h { |field| [field, hash[field.to_s]] })
+        end
+      end
+
+      # HTTP answer, including the X-TimeLogic-Signature* headers when signing is enabled.
+      RawResponse = Struct.new(:status, :headers, :body, keyword_init: true)
+
+      # Raised for any non-2xx answer. +error+ is the worldtimeapi.org-style message (for
+      # example "unknown location") or the TimeLogic message for authentication and quota errors.
+      class Error < StandardError
+        attr_reader :status, :error, :code, :body
+
+        def initialize(status, error, code, body)
+          super("WorldTimeAPI-compatible request failed (#{status}): #{error}")
+          @status = status
+          @error = error
+          @code = code
+          @body = body
+        end
+
+        def unknown_location?
+          status == 404 && error == 'unknown location'
+        end
+
+        def malformed_ip?
+          status == 404 && error == 'malformed ip'
+        end
+      end
+
+      # The 404 {"error":"unknown location"} answer.
+      class UnknownLocationError < Error; end
+
+      def self.error_from_response(status, body)
+        message = body.to_s.strip
+        code = nil
+        if message.start_with?('Error:')
+          message = message.delete_prefix('Error:').strip
+        else
+          begin
+            parsed = JSON.parse(body.to_s)
+            if parsed.is_a?(Hash) && parsed.key?('error')
+              if parsed['error'].is_a?(String)
+                message = parsed['error']
+              elsif parsed['error'].is_a?(Hash)
+                message = parsed['error']['message'].to_s
+                code = parsed['error']['code']&.to_s
+              end
+            end
+          rescue JSON::ParserError
+            # keep the raw body as the message
+          end
+        end
+        klass = status == 404 && message == 'unknown location' ? UnknownLocationError : Error
+        klass.new(status, message, code, body.to_s)
+      end
+
+      # Path for "Europe/London", "America/Argentina/Salta" or a one-word zone such as "UTC".
+      def self.zone_path(timezone, text = false)
+        segments = timezone.to_s.split('/').reject(&:empty?)
+        unless (1..3).cover?(segments.length)
+          raise ArgumentError, 'timezone must have one to three segments, for example "Europe/London"'
+        end
+
+        "/api/timezone/#{segments.map { |s| URI.encode_www_form_component(s).gsub('+', '%20') }.join('/')}#{text ? '.txt' : ''}"
+      end
+
+      def self.ip_path(ip = nil, text = false)
+        base = ip.nil? || ip.to_s.empty? ? '/api/ip' : "/api/ip/#{URI.encode_www_form_component(ip.to_s)}"
+        "#{base}#{text ? '.txt' : ''}"
+      end
+
+      # Client for the WorldTimeAPI-compatible routes.
+      class Client
+        # transport: optional callable (url, headers) -> RawResponse, used by tests.
+        def initialize(api_key:, base_url: DEFAULT_BASE_URL, sign: false, timeout: 30, transport: nil)
+          raise ArgumentError, 'api_key is required' if api_key.nil? || api_key.to_s.empty?
+
+          @api_key = api_key.to_s
+          @base_url = base_url.to_s.sub(%r{/+\z}, '')
+          @sign = sign
+          @timeout = timeout
+          @transport = transport
+        end
+
+        # GET /api/timezone
+        def list_timezones
+          get_json('/api/timezone')
+        end
+
+        # GET /api/timezone.txt
+        def list_timezones_text
+          get_text('/api/timezone.txt')
+        end
+
+        # GET /api/timezone/{area}
+        def list_timezones_in_area(area)
+          value = get_json(WorldTimeApi.zone_path(area))
+          raise Error.new(200, "#{area} is a timezone, not an area; use get_timezone", nil, JSON.generate(value)) unless value.is_a?(Array)
+
+          value
+        end
+
+        # GET /api/timezone/{area}.txt
+        def list_timezones_in_area_text(area)
+          get_text(WorldTimeApi.zone_path(area, true))
+        end
+
+        # GET /api/timezone/{area}/{location}[/{region}], or a one-word zone such as UTC.
+        def get_timezone(timezone)
+          DateTime.from_hash(get_json(WorldTimeApi.zone_path(timezone)))
+        end
+
+        def get_timezone_text(timezone)
+          get_text(WorldTimeApi.zone_path(timezone, true))
+        end
+
+        # GET /api/ip (the caller's address) or /api/ip/{ip}.
+        def get_ip(ip = nil)
+          DateTime.from_hash(get_json(WorldTimeApi.ip_path(ip)))
+        end
+
+        def get_ip_text(ip = nil)
+          get_text(WorldTimeApi.ip_path(ip, true))
+        end
+
+        # GET any /api/* path and return status, headers and body without raising.
+        def request_raw(path)
+          url = "#{@base_url}#{path}#{@sign ? '?sign=true' : ''}"
+          headers = { 'X-API-Key' => @api_key, 'Accept' => path.end_with?('.txt') ? 'text/plain' : 'application/json' }
+          return @transport.call(url, headers) if @transport
+
+          uri = URI.parse(url)
+          http = Net::HTTP.new(uri.host, uri.port)
+          http.use_ssl = uri.scheme == 'https'
+          http.open_timeout = @timeout
+          http.read_timeout = @timeout
+          request = Net::HTTP::Get.new(uri.request_uri)
+          headers.each { |name, value| request[name] = value }
+          response = http.request(request)
+          RawResponse.new(
+            status: response.code.to_i,
+            headers: response.each_header.to_h { |name, value| [name.downcase, value] },
+            body: response.body.to_s.dup.force_encoding('UTF-8')
+          )
+        end
+
+        private
+
+        def get_text(path)
+          raw = request_raw(path)
+          raise WorldTimeApi.error_from_response(raw.status, raw.body) unless (200..299).cover?(raw.status)
+
+          raw.body
+        end
+
+        def get_json(path)
+          JSON.parse(get_text(path))
+        end
+      end
+    end
+  end
+end

data/lib/timelogic-api.rb

@@ -4,7 +4,7 @@ end
 =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
 
@@ -61,3 +61,4 @@ module TimeLogic::Api
     end
   end
 end
+require 'timelogic-api/world_time_api'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: timelogic-api
 version: !ruby/object:Gem::Version
-  version: 1.0.3
+  version: 1.1.0
 platform: ruby
 authors:
 - TimeLogic API LLC
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-29 00:00:00.000000000 Z
+date: 2026-11-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: typhoeus
@@ -105,6 +105,7 @@ files:
 - lib/timelogic-api/models/timezone_resolved_response.rb
 - lib/timelogic-api/transport_configuration.rb
 - lib/timelogic-api/version.rb
+- lib/timelogic-api/world_time_api.rb
 homepage: https://github.com/TimeLogic-API-LLC/timelogic-api-sdks
 licenses:
 - Unlicense