zernio-sdk 0.0.734 → 0.0.736

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b14a2c7fb924c02a121a59e55c941aaf52fa196ba30d6f3334e1adc791557a2c
-  data.tar.gz: b830a945dd84db77689292597a88d3b669326fbeb94ed7c35b74747bb122fe38
+  metadata.gz: 63ca4050c220902da4e303732c62730c080426df1b5779d07f880d5e8bb45f02
+  data.tar.gz: b4c23c0f20c1ff9fbb9514d4f09847b0463019c69ef870e31eac94f41fd81330
 SHA512:
-  metadata.gz: 2bdd5fd51e2f00f5308d2e95d48b13e66189c7b05543b0f46261bb9e8039dbd8fa783866da5babd0c381f13e9f6fbae4ec6f98f9067b176105f6ab087a4b56ee
-  data.tar.gz: ff72978a89ba6580323ed66f16fb50a879f56031eff625b2d1c8ab90303f810d268440670bc30f0b22c58f62cca1604ec609c181d39d404551eeaf2e7fc4069f
+  metadata.gz: 1fff3ac80df8810b1675b28aee89741ea1845acafb0c0dde26667881f58842fd515f9f829445cad95cc23e7121f03a7dd226bc3fe2c1f62d5f242d9bbd42ba05
+  data.tar.gz: 5c42494461e13f84907cd5e3fa40500d54481d6759890428b902e6ff171cae18fc98f72d77c31eebff64527a2341f33b45ba3d0e0e714349e132c1b08385b06f

data/docs/ConnectApi.md

@@ -631,7 +631,7 @@ end
 
 Connect WhatsApp via credentials
 
-Connect a WhatsApp Business Account by providing Meta credentials directly. This is the headless alternative to the Embedded Signup browser flow.  To get the required credentials: 1. Go to Meta Business Suite (business.facebook.com) 2. Create or select a WhatsApp Business Account 3. In Business Settings > System Users, create a System User 4. Assign it the whatsapp_business_management and whatsapp_business_messaging permissions 5. Generate a permanent access token 6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers 7. Get the Phone Number ID from the same page (click on the number) 
+Connect a WhatsApp Business Account by providing Meta credentials directly. This is the headless alternative to the Embedded Signup browser flow.  To get the required credentials: 1. Go to Meta Business Suite (business.facebook.com) 2. Create or select a WhatsApp Business Account 3. In Business Settings > System Users, create a System User 4. Assign it the whatsapp_business_management and whatsapp_business_messaging permissions 5. Generate a permanent access token 6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers 7. Get the Phone Number ID from the same page (click on the number)  Warning: connecting subscribes your own Meta app to this WABA with an override callback that redirects its webhook delivery to Zernio. This WABA's events stop reaching any callback URL you had configured before, immediately and with no overlap window. Do not unsubscribe your app from the WABA afterward: that also cuts off Zernio's delivery, and recovery requires calling this endpoint again. 
 
 ### Examples
 

data/docs/ConnectWhatsAppCredentials200Response.md

@@ -6,6 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **message** | **String** |  | [optional] |
 | **registration_warning** | **String** | Present when the account was created but Meta rejected the Cloud API registration. The number cannot send messages until this is resolved. | [optional] |
+| **webhook_notice** | **String** | Present when the WABA webhook subscription (with the Zernio override callback) succeeded. Explains the delivery cutover and warns against unsubscribing the app from the WABA afterward. | [optional] |
 | **account** | [**ConnectWhatsAppCredentials200ResponseAccount**](ConnectWhatsAppCredentials200ResponseAccount.md) |  | [optional] |
 
 ## Example
@@ -16,6 +17,7 @@ require 'zernio-sdk'
 instance = Zernio::ConnectWhatsAppCredentials200Response.new(
   message: null,
   registration_warning: null,
+  webhook_notice: null,
   account: null
 )
 ```

data/docs/ConnectWhatsAppCredentials200ResponseAccount.md

@@ -9,7 +9,9 @@
 | **username** | **String** | Display phone number | [optional] |
 | **display_name** | **String** | Meta-verified business name | [optional] |
 | **is_active** | **Boolean** |  | [optional] |
-| **selected_phone_number** | **String** | The connected phone number | [optional] |
+| **phone_number** | **String** | The connected phone number | [optional] |
+| **verified_name** | **String** | Meta-verified business name for the phone number | [optional] |
+| **quality_rating** | **String** | Meta quality rating for the phone number (e.g. GREEN, YELLOW, RED, UNKNOWN) | [optional] |
 
 ## Example
 
@@ -22,7 +24,9 @@ instance = Zernio::ConnectWhatsAppCredentials200ResponseAccount.new(
   username: null,
   display_name: null,
   is_active: null,
-  selected_phone_number: null
+  phone_number: null,
+  verified_name: null,
+  quality_rating: null
 )
 ```
 

data/docs/InboxWebhookMessage.md

@@ -12,7 +12,7 @@
 | **text** | **String** | Message text content (retained on deleted messages for API consumers; Zernio dashboard UI hides this) |  |
 | **attachments** | [**Array<InboxWebhookMessageAttachmentsInner>**](InboxWebhookMessageAttachmentsInner.md) |  |  |
 | **sender** | [**InboxWebhookMessageSender**](InboxWebhookMessageSender.md) |  |  |
-| **sent_at** | **Time** |  |  |
+| **sent_at** | **Time** | When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order. |  |
 | **is_read** | **Boolean** |  |  |
 
 ## Example

data/docs/WebhookPayloadMessageMessage.md

@@ -12,7 +12,7 @@
 | **text** | **String** | Message text content |  |
 | **attachments** | [**Array<WebhookPayloadMessageMessageAttachmentsInner>**](WebhookPayloadMessageMessageAttachmentsInner.md) |  |  |
 | **sender** | [**WebhookPayloadMessageMessageSender**](WebhookPayloadMessageMessageSender.md) |  |  |
-| **sent_at** | **Time** |  |  |
+| **sent_at** | **Time** | When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order. |  |
 | **is_read** | **Boolean** |  |  |
 
 ## Example

data/docs/WebhookPayloadMessageSentMessage.md

@@ -12,7 +12,7 @@
 | **text** | **String** | Message text content |  |
 | **attachments** | [**Array<WebhookPayloadMessageSentMessageAttachmentsInner>**](WebhookPayloadMessageSentMessageAttachmentsInner.md) |  |  |
 | **sender** | [**WebhookPayloadMessageSentMessageSender**](WebhookPayloadMessageSentMessageSender.md) |  |  |
-| **sent_at** | **Time** |  |  |
+| **sent_at** | **Time** | When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order. |  |
 | **is_read** | **Boolean** |  |  |
 | **source** | **String** | WhatsApp send origin. whatsapp_business_app when sent from the WhatsApp Business phone app on a Coexistence number; cloud_api when sent through Zernio (dashboard, API, or broadcasts). Absent on non-WhatsApp platforms. This is not the inbox metadata.source lineage field. | [optional] |
 

data/lib/zernio-sdk/api/connect_api.rb

@@ -594,7 +594,7 @@ module Zernio
     end
 
     # Connect WhatsApp via credentials
-    # Connect a WhatsApp Business Account by providing Meta credentials directly. This is the headless alternative to the Embedded Signup browser flow.  To get the required credentials: 1. Go to Meta Business Suite (business.facebook.com) 2. Create or select a WhatsApp Business Account 3. In Business Settings > System Users, create a System User 4. Assign it the whatsapp_business_management and whatsapp_business_messaging permissions 5. Generate a permanent access token 6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers 7. Get the Phone Number ID from the same page (click on the number) 
+    # Connect a WhatsApp Business Account by providing Meta credentials directly. This is the headless alternative to the Embedded Signup browser flow.  To get the required credentials: 1. Go to Meta Business Suite (business.facebook.com) 2. Create or select a WhatsApp Business Account 3. In Business Settings > System Users, create a System User 4. Assign it the whatsapp_business_management and whatsapp_business_messaging permissions 5. Generate a permanent access token 6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers 7. Get the Phone Number ID from the same page (click on the number)  Warning: connecting subscribes your own Meta app to this WABA with an override callback that redirects its webhook delivery to Zernio. This WABA's events stop reaching any callback URL you had configured before, immediately and with no overlap window. Do not unsubscribe your app from the WABA afterward: that also cuts off Zernio's delivery, and recovery requires calling this endpoint again. 
     # @param connect_whats_app_credentials_request [ConnectWhatsAppCredentialsRequest] 
     # @param [Hash] opts the optional parameters
     # @return [ConnectWhatsAppCredentials200Response]
@@ -604,7 +604,7 @@ module Zernio
     end
 
     # Connect WhatsApp via credentials
-    # Connect a WhatsApp Business Account by providing Meta credentials directly. This is the headless alternative to the Embedded Signup browser flow.  To get the required credentials: 1. Go to Meta Business Suite (business.facebook.com) 2. Create or select a WhatsApp Business Account 3. In Business Settings > System Users, create a System User 4. Assign it the whatsapp_business_management and whatsapp_business_messaging permissions 5. Generate a permanent access token 6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers 7. Get the Phone Number ID from the same page (click on the number) 
+    # Connect a WhatsApp Business Account by providing Meta credentials directly. This is the headless alternative to the Embedded Signup browser flow.  To get the required credentials: 1. Go to Meta Business Suite (business.facebook.com) 2. Create or select a WhatsApp Business Account 3. In Business Settings > System Users, create a System User 4. Assign it the whatsapp_business_management and whatsapp_business_messaging permissions 5. Generate a permanent access token 6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers 7. Get the Phone Number ID from the same page (click on the number)  Warning: connecting subscribes your own Meta app to this WABA with an override callback that redirects its webhook delivery to Zernio. This WABA's events stop reaching any callback URL you had configured before, immediately and with no overlap window. Do not unsubscribe your app from the WABA afterward: that also cuts off Zernio's delivery, and recovery requires calling this endpoint again. 
     # @param connect_whats_app_credentials_request [ConnectWhatsAppCredentialsRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(ConnectWhatsAppCredentials200Response, Integer, Hash)>] ConnectWhatsAppCredentials200Response data, response status code and response headers

data/lib/zernio-sdk/models/connect_whats_app_credentials200_response.rb

@@ -20,6 +20,9 @@ module Zernio
     # Present when the account was created but Meta rejected the Cloud API registration. The number cannot send messages until this is resolved.
     attr_accessor :registration_warning
 
+    # Present when the WABA webhook subscription (with the Zernio override callback) succeeded. Explains the delivery cutover and warns against unsubscribing the app from the WABA afterward.
+    attr_accessor :webhook_notice
+
     attr_accessor :account
 
     # Attribute mapping from ruby-style variable name to JSON key.
@@ -27,6 +30,7 @@ module Zernio
       {
         :'message' => :'message',
         :'registration_warning' => :'registrationWarning',
+        :'webhook_notice' => :'webhookNotice',
         :'account' => :'account'
       }
     end
@@ -46,6 +50,7 @@ module Zernio
       {
         :'message' => :'String',
         :'registration_warning' => :'String',
+        :'webhook_notice' => :'String',
         :'account' => :'ConnectWhatsAppCredentials200ResponseAccount'
       }
     end
@@ -80,6 +85,10 @@ module Zernio
         self.registration_warning = attributes[:'registration_warning']
       end
 
+      if attributes.key?(:'webhook_notice')
+        self.webhook_notice = attributes[:'webhook_notice']
+      end
+
       if attributes.key?(:'account')
         self.account = attributes[:'account']
       end
@@ -107,6 +116,7 @@ module Zernio
       self.class == o.class &&
           message == o.message &&
           registration_warning == o.registration_warning &&
+          webhook_notice == o.webhook_notice &&
           account == o.account
     end
 
@@ -119,7 +129,7 @@ module Zernio
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [message, registration_warning, account].hash
+      [message, registration_warning, webhook_notice, account].hash
     end
 
     # Builds the object from hash

data/lib/zernio-sdk/models/connect_whats_app_credentials200_response_account.rb

@@ -28,7 +28,13 @@ module Zernio
     attr_accessor :is_active
 
     # The connected phone number
-    attr_accessor :selected_phone_number
+    attr_accessor :phone_number
+
+    # Meta-verified business name for the phone number
+    attr_accessor :verified_name
+
+    # Meta quality rating for the phone number (e.g. GREEN, YELLOW, RED, UNKNOWN)
+    attr_accessor :quality_rating
 
     class EnumAttributeValidator
       attr_reader :datatype
@@ -60,7 +66,9 @@ module Zernio
         :'username' => :'username',
         :'display_name' => :'displayName',
         :'is_active' => :'isActive',
-        :'selected_phone_number' => :'selectedPhoneNumber'
+        :'phone_number' => :'phoneNumber',
+        :'verified_name' => :'verifiedName',
+        :'quality_rating' => :'qualityRating'
       }
     end
 
@@ -82,7 +90,9 @@ module Zernio
         :'username' => :'String',
         :'display_name' => :'String',
         :'is_active' => :'Boolean',
-        :'selected_phone_number' => :'String'
+        :'phone_number' => :'String',
+        :'verified_name' => :'String',
+        :'quality_rating' => :'String'
       }
     end
 
@@ -128,8 +138,16 @@ module Zernio
         self.is_active = attributes[:'is_active']
       end
 
-      if attributes.key?(:'selected_phone_number')
-        self.selected_phone_number = attributes[:'selected_phone_number']
+      if attributes.key?(:'phone_number')
+        self.phone_number = attributes[:'phone_number']
+      end
+
+      if attributes.key?(:'verified_name')
+        self.verified_name = attributes[:'verified_name']
+      end
+
+      if attributes.key?(:'quality_rating')
+        self.quality_rating = attributes[:'quality_rating']
       end
     end
 
@@ -170,7 +188,9 @@ module Zernio
           username == o.username &&
           display_name == o.display_name &&
           is_active == o.is_active &&
-          selected_phone_number == o.selected_phone_number
+          phone_number == o.phone_number &&
+          verified_name == o.verified_name &&
+          quality_rating == o.quality_rating
     end
 
     # @see the `==` method
@@ -182,7 +202,7 @@ module Zernio
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [account_id, platform, username, display_name, is_active, selected_phone_number].hash
+      [account_id, platform, username, display_name, is_active, phone_number, verified_name, quality_rating].hash
     end
 
     # Builds the object from hash

data/lib/zernio-sdk/models/inbox_webhook_message.rb

@@ -36,6 +36,7 @@ module Zernio
 
     attr_accessor :sender
 
+    # When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.
     attr_accessor :sent_at
 
     attr_accessor :is_read

data/lib/zernio-sdk/models/webhook_payload_message_message.rb

@@ -35,6 +35,7 @@ module Zernio
 
     attr_accessor :sender
 
+    # When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.
     attr_accessor :sent_at
 
     attr_accessor :is_read

data/lib/zernio-sdk/models/webhook_payload_message_sent_message.rb

@@ -35,6 +35,7 @@ module Zernio
 
     attr_accessor :sender
 
+    # When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.
     attr_accessor :sent_at
 
     attr_accessor :is_read

data/lib/zernio-sdk/version.rb

@@ -11,5 +11,5 @@ Generator version: 7.19.0
 =end
 
 module Zernio
-  VERSION = '0.0.734'
+  VERSION = '0.0.736'
 end

data/openapi.yaml

@@ -3287,6 +3287,7 @@ components:
         sentAt:
           type: string
           format: date-time
+          description: 'When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.'
         isRead:
           type: boolean
     InboxWebhookConversation:
@@ -3588,6 +3589,7 @@ components:
             sentAt:
               type: string
               format: date-time
+              description: 'When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.'
             isRead:
               type: boolean
         conversation:
@@ -3929,6 +3931,7 @@ components:
             sentAt:
               type: string
               format: date-time
+              description: 'When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.'
             isRead:
               type: boolean
             source:
@@ -20489,6 +20492,12 @@ paths:
         5. Generate a permanent access token
         6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers
         7. Get the Phone Number ID from the same page (click on the number)
+
+        Warning: connecting subscribes your own Meta app to this WABA with an override
+        callback that redirects its webhook delivery to Zernio. This WABA's events stop
+        reaching any callback URL you had configured before, immediately and with no
+        overlap window. Do not unsubscribe your app from the WABA afterward: that also
+        cuts off Zernio's delivery, and recovery requires calling this endpoint again.
       security:
         - bearerAuth: []
       requestBody:
@@ -20533,6 +20542,9 @@ paths:
                   registrationWarning:
                     type: string
                     description: 'Present when the account was created but Meta rejected the Cloud API registration. The number cannot send messages until this is resolved.'
+                  webhookNotice:
+                    type: string
+                    description: 'Present when the WABA webhook subscription (with the Zernio override callback) succeeded. Explains the delivery cutover and warns against unsubscribing the app from the WABA afterward.'
                   account:
                     type: object
                     properties:
@@ -20541,7 +20553,9 @@ paths:
                       username: { type: string, description: Display phone number }
                       displayName: { type: string, description: Meta-verified business name }
                       isActive: { type: boolean }
-                      selectedPhoneNumber: { type: string, description: The connected phone number }
+                      phoneNumber: { type: string, description: The connected phone number }
+                      verifiedName: { type: string, description: Meta-verified business name for the phone number }
+                      qualityRating: { type: string, description: 'Meta quality rating for the phone number (e.g. GREEN, YELLOW, RED, UNKNOWN)' }
               example:
                 message: "WhatsApp connected successfully"
                 account:
@@ -20550,7 +20564,9 @@ paths:
                   username: "+1 555-123-4567"
                   displayName: "Acme Corp"
                   isActive: true
-                  selectedPhoneNumber: "+1 555-123-4567"
+                  phoneNumber: "+1 555-123-4567"
+                  verifiedName: "Acme Corp"
+                  qualityRating: "GREEN"
         '400':
           description: |
             Invalid request. Missing fields, a `pin` that is not 6 digits, or the

data/spec/api/connect_api_spec.rb

@@ -139,7 +139,7 @@ describe 'ConnectApi' do
 
   # unit tests for connect_whats_app_credentials
   # Connect WhatsApp via credentials
-  # Connect a WhatsApp Business Account by providing Meta credentials directly. This is the headless alternative to the Embedded Signup browser flow.  To get the required credentials: 1. Go to Meta Business Suite (business.facebook.com) 2. Create or select a WhatsApp Business Account 3. In Business Settings > System Users, create a System User 4. Assign it the whatsapp_business_management and whatsapp_business_messaging permissions 5. Generate a permanent access token 6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers 7. Get the Phone Number ID from the same page (click on the number) 
+  # Connect a WhatsApp Business Account by providing Meta credentials directly. This is the headless alternative to the Embedded Signup browser flow.  To get the required credentials: 1. Go to Meta Business Suite (business.facebook.com) 2. Create or select a WhatsApp Business Account 3. In Business Settings > System Users, create a System User 4. Assign it the whatsapp_business_management and whatsapp_business_messaging permissions 5. Generate a permanent access token 6. Get the WABA ID from WhatsApp Manager > Account Tools > Phone Numbers 7. Get the Phone Number ID from the same page (click on the number)  Warning: connecting subscribes your own Meta app to this WABA with an override callback that redirects its webhook delivery to Zernio. This WABA's events stop reaching any callback URL you had configured before, immediately and with no overlap window. Do not unsubscribe your app from the WABA afterward: that also cuts off Zernio's delivery, and recovery requires calling this endpoint again. 
   # @param connect_whats_app_credentials_request 
   # @param [Hash] opts the optional parameters
   # @return [ConnectWhatsAppCredentials200Response]

data/spec/models/connect_whats_app_credentials200_response_account_spec.rb

@@ -61,7 +61,19 @@ describe Zernio::ConnectWhatsAppCredentials200ResponseAccount do
     end
   end
 
-  describe 'test attribute "selected_phone_number"' do
+  describe 'test attribute "phone_number"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "verified_name"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "quality_rating"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/models/connect_whats_app_credentials200_response_spec.rb

@@ -39,6 +39,12 @@ describe Zernio::ConnectWhatsAppCredentials200Response do
     end
   end
 
+  describe 'test attribute "webhook_notice"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "account"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: zernio-sdk
 version: !ruby/object:Gem::Version
-  version: 0.0.734
+  version: 0.0.736
 platform: ruby
 authors:
 - OpenAPI-Generator