constant_contact_client 1.0.0 → 1.5.0

data/lib/constant_contact_client/api/contacts_api.rb

@@ -1,9 +1,9 @@
 =begin
 #Constant Contact API v3
 
-#Swagger build version 3.0.2475
+#Swagger build version 3.0.161
 
-The version of the OpenAPI document: 1.0.101
+The version of the OpenAPI document: 1.0.220
 Contact: webservices@constantcontact.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.2.0
@@ -20,7 +20,7 @@ module ConstantContactClient
       @api_client = api_client
     end
     # POST (create) a Contact
-    # Creates a new contact resource; you must include the `create_source` property and at least one of the following properties when creating a new contact: `first_name`, `last_name`, or `email_address` (`email_address` must be unique for each contact).
+    #  Creates a new contact resource. You must include the `create_source` property and at least one of the following properties: `first_name`, `last_name`, a unique `email_address` (specified using the `EmailAddress` object), or the `sms_channel` property (specified using the `ContactSmsChannel` object).  <div class=\"Msg\"><p class=\"note-text\">If `email_address` is specified: **Only use this method when a contact gives you their explicit permission to send them an email. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.</p></div>  If `sms_channel` is specified: <div class=\"Msg\"><p class=\"note-text\">Only use this method when a contact gives you their explicit permission to send them an SMS. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.</p></div>
     # @param create_contact_request [CreateContactRequest] The JSON payload defining the contact
     # @param [Hash] opts the optional parameters
     # @return [GetContactById200Response]
@@ -30,7 +30,7 @@ module ConstantContactClient
     end
 
     # POST (create) a Contact
-    # Creates a new contact resource; you must include the &#x60;create_source&#x60; property and at least one of the following properties when creating a new contact: &#x60;first_name&#x60;, &#x60;last_name&#x60;, or &#x60;email_address&#x60; (&#x60;email_address&#x60; must be unique for each contact).
+    #  Creates a new contact resource. You must include the &#x60;create_source&#x60; property and at least one of the following properties: &#x60;first_name&#x60;, &#x60;last_name&#x60;, a unique &#x60;email_address&#x60; (specified using the &#x60;EmailAddress&#x60; object), or the &#x60;sms_channel&#x60; property (specified using the &#x60;ContactSmsChannel&#x60; object).  &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt;If &#x60;email_address&#x60; is specified: **Only use this method when a contact gives you their explicit permission to send them an email. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.&lt;/p&gt;&lt;/div&gt;  If &#x60;sms_channel&#x60; is specified: &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt;Only use this method when a contact gives you their explicit permission to send them an SMS. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.&lt;/p&gt;&lt;/div&gt;
     # @param create_contact_request [CreateContactRequest] The JSON payload defining the contact
     # @param [Hash] opts the optional parameters
     # @return [Array<(GetContactById200Response, Integer, Hash)>] GetContactById200Response data, response status code and response headers
@@ -88,8 +88,8 @@ module ConstantContactClient
     end
 
     # Create or Update a Contact
-    # Use this method to create a new contact or update an existing contact. This method uses the `email_address` string value you include in the request body to determine if it should create an new contact or update an existing contact.  Updates to existing contacts are partial updates. This method only updates the contact properties you include in the request body. Updates append new contact lists or custom fields to the existing `list_memberships` or `custom_fields` arrays. <div class=\"Msg\"><p class=\"note-text\">Only use this method when a contact gives you their explicit permission to send them emails. It is a violation of US and Canadian anti-spam laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.</p></div>  When this method creates a new contact, it returns a 201 response code.  When this method updates an existing contact, it returns a 200 response code. Updating a deleted contact restores the contact.  The method automatically modifies the contact's `permission_to_send` and `opt_in_source` properties depending on the [Confirmed Opt-In](https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5533-obtain-permission-to-send-email-campaigns-to-your-contacts-by-using-confirmed-opt-in) Constant Contact account setting:  If Confirmed Opt-in is _enabled_, this method automatically sets the `permission_to_send` property as pending\\_confirmation for new contacts.   If Confirmed Opt-in is _disabled_, this method automatically sets the `permission_to_send` property as explicit and the `opt_in_source` property as `Contact` for new contacts. Updated contacts have their `permission_to_send` property set as explicit.       
-    # @param create_or_update_contact_request [CreateOrUpdateContactRequest] A JSON request body payload that contains the contact resource you are creating or updating. The request body must contain the &#x60;email_address&#x60; property and the &#x60;list_memberships&#x60; array.
+    # Use this method to create a new contact or update an existing contact. In the request body, this method requires including the `list_memberships` array as well as either the contact's `email_address` string or `sms_channel` object which includes the contact's SMS number. The information you specify determines if a new contact is either created (the email address or SMS number does not already exist in the account), or if an existing contact is updated (the email address or SMS number already exists). The SMS product feature does not need to be enabled to include a contacts SMS details.  Updates to existing contacts are partial updates. This method only updates the contact properties you include in the request body. Updates append new contact lists or custom fields to the existing `list_memberships` or `custom_fields` arrays.  If `email_address` is specified: <div class=\"Msg\"><p class=\"note-text\">Only use this method when a contact gives you their explicit permission to send them an email. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.</p></div>  If `sms_channel` is specified: <div class=\"Msg\"><p class=\"note-text\">Only use this method when a contact gives you their explicit permission to send them an SMS. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.</p></div>  When this method creates a new contact, it returns a 201 response code.When this method updates an existing contact, it returns a 200 response code. Updating a deleted contact restores the contact.  The method automatically modifies the contact's `permission_to_send` and `opt_in_source` properties depending on the [Confirmed Opt-In](https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5533-obtain-permission-to-send-email-campaigns-to-your-contacts-by-using-confirmed-opt-in) Constant Contact account setting:  If Confirmed Opt-in is _enabled_, this method automatically sets the `permission_to_send` property as `pending_confirmation` for new contacts. If Confirmed Opt-in is _disabled_, this method automatically sets the `permission_to_send` property as explicit and the `opt_in_source` property as `Contact` for new contacts. Updated contacts have their `permission_to_send` property set as explicit.       
+    # @param create_or_update_contact_request [CreateOrUpdateContactRequest] A JSON request body payload that contains the contact resource you are creating or updating. The request body must contain the &#x60;email_address&#x60; property and &#x60;list_memberships&#x60; array, or the &#x60;sms_channel&#x60; object.
     # @param [Hash] opts the optional parameters
     # @return [CreateOrUpdateContact200Response]
     def create_or_update_contact(create_or_update_contact_request, opts = {})
@@ -98,8 +98,8 @@ module ConstantContactClient
     end
 
     # Create or Update a Contact
-    # Use this method to create a new contact or update an existing contact. This method uses the &#x60;email_address&#x60; string value you include in the request body to determine if it should create an new contact or update an existing contact.  Updates to existing contacts are partial updates. This method only updates the contact properties you include in the request body. Updates append new contact lists or custom fields to the existing &#x60;list_memberships&#x60; or &#x60;custom_fields&#x60; arrays. &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt;Only use this method when a contact gives you their explicit permission to send them emails. It is a violation of US and Canadian anti-spam laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.&lt;/p&gt;&lt;/div&gt;  When this method creates a new contact, it returns a 201 response code.  When this method updates an existing contact, it returns a 200 response code. Updating a deleted contact restores the contact.  The method automatically modifies the contact&#39;s &#x60;permission_to_send&#x60; and &#x60;opt_in_source&#x60; properties depending on the [Confirmed Opt-In](https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5533-obtain-permission-to-send-email-campaigns-to-your-contacts-by-using-confirmed-opt-in) Constant Contact account setting:  If Confirmed Opt-in is _enabled_, this method automatically sets the &#x60;permission_to_send&#x60; property as pending\\_confirmation for new contacts.   If Confirmed Opt-in is _disabled_, this method automatically sets the &#x60;permission_to_send&#x60; property as explicit and the &#x60;opt_in_source&#x60; property as &#x60;Contact&#x60; for new contacts. Updated contacts have their &#x60;permission_to_send&#x60; property set as explicit.       
-    # @param create_or_update_contact_request [CreateOrUpdateContactRequest] A JSON request body payload that contains the contact resource you are creating or updating. The request body must contain the &#x60;email_address&#x60; property and the &#x60;list_memberships&#x60; array.
+    # Use this method to create a new contact or update an existing contact. In the request body, this method requires including the &#x60;list_memberships&#x60; array as well as either the contact&#39;s &#x60;email_address&#x60; string or &#x60;sms_channel&#x60; object which includes the contact&#39;s SMS number. The information you specify determines if a new contact is either created (the email address or SMS number does not already exist in the account), or if an existing contact is updated (the email address or SMS number already exists). The SMS product feature does not need to be enabled to include a contacts SMS details.  Updates to existing contacts are partial updates. This method only updates the contact properties you include in the request body. Updates append new contact lists or custom fields to the existing &#x60;list_memberships&#x60; or &#x60;custom_fields&#x60; arrays.  If &#x60;email_address&#x60; is specified: &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt;Only use this method when a contact gives you their explicit permission to send them an email. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.&lt;/p&gt;&lt;/div&gt;  If &#x60;sms_channel&#x60; is specified: &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt;Only use this method when a contact gives you their explicit permission to send them an SMS. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.&lt;/p&gt;&lt;/div&gt;  When this method creates a new contact, it returns a 201 response code.When this method updates an existing contact, it returns a 200 response code. Updating a deleted contact restores the contact.  The method automatically modifies the contact&#39;s &#x60;permission_to_send&#x60; and &#x60;opt_in_source&#x60; properties depending on the [Confirmed Opt-In](https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5533-obtain-permission-to-send-email-campaigns-to-your-contacts-by-using-confirmed-opt-in) Constant Contact account setting:  If Confirmed Opt-in is _enabled_, this method automatically sets the &#x60;permission_to_send&#x60; property as &#x60;pending_confirmation&#x60; for new contacts. If Confirmed Opt-in is _disabled_, this method automatically sets the &#x60;permission_to_send&#x60; property as explicit and the &#x60;opt_in_source&#x60; property as &#x60;Contact&#x60; for new contacts. Updated contacts have their &#x60;permission_to_send&#x60; property set as explicit.       
+    # @param create_or_update_contact_request [CreateOrUpdateContactRequest] A JSON request body payload that contains the contact resource you are creating or updating. The request body must contain the &#x60;email_address&#x60; property and &#x60;list_memberships&#x60; array, or the &#x60;sms_channel&#x60; object.
     # @param [Hash] opts the optional parameters
     # @return [Array<(CreateOrUpdateContact200Response, Integer, Hash)>] CreateOrUpdateContact200Response data, response status code and response headers
     def create_or_update_contact_with_http_info(create_or_update_contact_request, opts = {})
@@ -217,7 +217,7 @@ module ConstantContactClient
     end
 
     # GET Contacts Collection
-    # Use this method to return a collection of contacts. Use the query parameters to search for contacts that match specific contact properties and subresourse properties as criteria. For example, you can search using the contact's `email` address, `lists` memberships, and by the date range that a contact was created or updated. Use the `limit` query parameter to limit the number of results returned per page. Use the `include` query parameter to include contact sub-resources in the response and `include_count` to include the total number of contacts that meet your specified search criteria.  By default, this method returns all contacts that are not deleted. Use the `status` query parameter with the value `all` to return all contacts including deleted contacts.
+    # Use this method to return a collection of contacts. Use the query parameters to search for contacts that match specific contact properties and sub-resource properties as criteria. For example, you can search using the contact's `email` address, `lists` memberships, and by the date range that a contact was created or updated. Use the `limit` query parameter to limit the number of results returned per page. Use the `include` query parameter to include contact sub-resources in the response and `include_count` to include the total number of contacts that meet your specified search criteria.  By default, this method returns all contacts that are not deleted. Use the `status` query parameter with the value `all` to return all contacts including deleted contacts.
     # @param [Hash] opts the optional parameters
     # @option opts [String] :status Use the &#x60;status&#x60; query parameter to search for contacts by status. This parameter accepts one or more comma separated values: &#x60;all&#x60;, &#x60;active&#x60;, &#x60;deleted&#x60;, &#x60;not_set&#x60;, &#x60;pending_confirmation&#x60;, &#x60;temp_hold&#x60;, and &#x60;unsubscribed&#x60;.
     # @option opts [String] :email Use the &#x60;email&#x60; query parameter to search for a contact using a specific email address.
@@ -230,7 +230,7 @@ module ConstantContactClient
     # @option opts [Time] :created_before Use &#x60;created_before&#x60; to search for contacts created before a specified date. To search for contacts created within a date range, specify both &#x60;created_after&#x60; and &#x60;created_before&#x60; dates. Accepts ISO-8601 formatted dates.
     # @option opts [Time] :optout_after Use &#x60;optout_after&#x60; to search for contacts that unsubscribed after a specified date.
     # @option opts [Time] :optout_before Use &#x60;optout_before&#x60; to search for contacts that unsubscribed before a specified date.
-    # @option opts [String] :include Use &#x60;include&#x60; to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: &#x60;custom_fields&#x60;, &#x60;list_memberships&#x60;, &#x60;taggings&#x60;, &#x60;notes&#x60;,&#x60;phone_numbers&#x60;, &#x60;street_addresses&#x60;, &#x60;sms_channel&#x60;.
+    # @option opts [String] :include Use &#x60;include&#x60; to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: &#x60;custom_fields&#x60;, &#x60;list_memberships&#x60;, &#x60;taggings&#x60;, &#x60;notes&#x60;,&#x60;phone_numbers&#x60;, &#x60;street_addresses&#x60;.
     # @option opts [String] :sms_status Use to get contacts by their SMS status. This parameter accepts one or more comma separated values: &#x60;all&#x60;, &#x60;explicit&#x60;, &#x60;unsubscribed&#x60;, &#x60;pending_confirmation&#x60;, &#x60;not_set&#x60;.
     # @option opts [Boolean] :include_count Set &#x60;include_count&#x3D;true&#x60; to include the total number of contacts (&#x60;contacts_count&#x60;) that meet all search criteria in the response body.
     # @option opts [Integer] :limit Specifies the number of results displayed per page of output in the response, from 1 - 500, default &#x3D; 50. (default to 50)
@@ -241,7 +241,7 @@ module ConstantContactClient
     end
 
     # GET Contacts Collection
-    # Use this method to return a collection of contacts. Use the query parameters to search for contacts that match specific contact properties and subresourse properties as criteria. For example, you can search using the contact&#39;s &#x60;email&#x60; address, &#x60;lists&#x60; memberships, and by the date range that a contact was created or updated. Use the &#x60;limit&#x60; query parameter to limit the number of results returned per page. Use the &#x60;include&#x60; query parameter to include contact sub-resources in the response and &#x60;include_count&#x60; to include the total number of contacts that meet your specified search criteria.  By default, this method returns all contacts that are not deleted. Use the &#x60;status&#x60; query parameter with the value &#x60;all&#x60; to return all contacts including deleted contacts.
+    # Use this method to return a collection of contacts. Use the query parameters to search for contacts that match specific contact properties and sub-resource properties as criteria. For example, you can search using the contact&#39;s &#x60;email&#x60; address, &#x60;lists&#x60; memberships, and by the date range that a contact was created or updated. Use the &#x60;limit&#x60; query parameter to limit the number of results returned per page. Use the &#x60;include&#x60; query parameter to include contact sub-resources in the response and &#x60;include_count&#x60; to include the total number of contacts that meet your specified search criteria.  By default, this method returns all contacts that are not deleted. Use the &#x60;status&#x60; query parameter with the value &#x60;all&#x60; to return all contacts including deleted contacts.
     # @param [Hash] opts the optional parameters
     # @option opts [String] :status Use the &#x60;status&#x60; query parameter to search for contacts by status. This parameter accepts one or more comma separated values: &#x60;all&#x60;, &#x60;active&#x60;, &#x60;deleted&#x60;, &#x60;not_set&#x60;, &#x60;pending_confirmation&#x60;, &#x60;temp_hold&#x60;, and &#x60;unsubscribed&#x60;.
     # @option opts [String] :email Use the &#x60;email&#x60; query parameter to search for a contact using a specific email address.
@@ -254,7 +254,7 @@ module ConstantContactClient
     # @option opts [Time] :created_before Use &#x60;created_before&#x60; to search for contacts created before a specified date. To search for contacts created within a date range, specify both &#x60;created_after&#x60; and &#x60;created_before&#x60; dates. Accepts ISO-8601 formatted dates.
     # @option opts [Time] :optout_after Use &#x60;optout_after&#x60; to search for contacts that unsubscribed after a specified date.
     # @option opts [Time] :optout_before Use &#x60;optout_before&#x60; to search for contacts that unsubscribed before a specified date.
-    # @option opts [String] :include Use &#x60;include&#x60; to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: &#x60;custom_fields&#x60;, &#x60;list_memberships&#x60;, &#x60;taggings&#x60;, &#x60;notes&#x60;,&#x60;phone_numbers&#x60;, &#x60;street_addresses&#x60;, &#x60;sms_channel&#x60;.
+    # @option opts [String] :include Use &#x60;include&#x60; to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: &#x60;custom_fields&#x60;, &#x60;list_memberships&#x60;, &#x60;taggings&#x60;, &#x60;notes&#x60;,&#x60;phone_numbers&#x60;, &#x60;street_addresses&#x60;.
     # @option opts [String] :sms_status Use to get contacts by their SMS status. This parameter accepts one or more comma separated values: &#x60;all&#x60;, &#x60;explicit&#x60;, &#x60;unsubscribed&#x60;, &#x60;pending_confirmation&#x60;, &#x60;not_set&#x60;.
     # @option opts [Boolean] :include_count Set &#x60;include_count&#x3D;true&#x60; to include the total number of contacts (&#x60;contacts_count&#x60;) that meet all search criteria in the response body.
     # @option opts [Integer] :limit Specifies the number of results displayed per page of output in the response, from 1 - 500, default &#x3D; 50. (default to 50)
@@ -267,7 +267,7 @@ module ConstantContactClient
       if @api_client.config.client_side_validation && opts[:'status'] && !allowable_values.include?(opts[:'status'])
         fail ArgumentError, "invalid value for \"status\", must be one of #{allowable_values}"
       end
-      allowable_values = ["custom_fields", "list_memberships", "phone_numbers", "street_addresses", "taggings", "notes", "sms_channel"]
+      allowable_values = ["custom_fields", "list_memberships", "phone_numbers", "street_addresses", "taggings", "notes"]
       if @api_client.config.client_side_validation && opts[:'include'] && !allowable_values.include?(opts[:'include'])
         fail ArgumentError, "invalid value for \"include\", must be one of #{allowable_values}"
       end
@@ -342,7 +342,7 @@ module ConstantContactClient
     # This endpoint GETs a specific contact resource (contact_id). Use the `include` query parameter to add any of the available contact sub-resources to the response payload.
     # @param contact_id [String] Unique ID of contact to GET
     # @param [Hash] opts the optional parameters
-    # @option opts [String] :include Use &#x60;include&#x60; to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: &#x60;custom_fields&#x60;, &#x60;list_memberships&#x60;, &#x60;phone_numbers&#x60;, &#x60;street_addresses&#x60;, &#x60;notes&#x60;, &#x60;sms_channel&#x60;, and &#x60;taggings&#x60;.
+    # @option opts [String] :include Use &#x60;include&#x60; to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: &#x60;custom_fields&#x60;, &#x60;list_memberships&#x60;, &#x60;phone_numbers&#x60;, &#x60;street_addresses&#x60;, &#x60;notes&#x60;, and &#x60;taggings&#x60;.
     # @return [GetContactById200Response]
     def get_contact_by_id(contact_id, opts = {})
       data, _status_code, _headers = get_contact_by_id_with_http_info(contact_id, opts)
@@ -353,7 +353,7 @@ module ConstantContactClient
     # This endpoint GETs a specific contact resource (contact_id). Use the &#x60;include&#x60; query parameter to add any of the available contact sub-resources to the response payload.
     # @param contact_id [String] Unique ID of contact to GET
     # @param [Hash] opts the optional parameters
-    # @option opts [String] :include Use &#x60;include&#x60; to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: &#x60;custom_fields&#x60;, &#x60;list_memberships&#x60;, &#x60;phone_numbers&#x60;, &#x60;street_addresses&#x60;, &#x60;notes&#x60;, &#x60;sms_channel&#x60;, and &#x60;taggings&#x60;.
+    # @option opts [String] :include Use &#x60;include&#x60; to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: &#x60;custom_fields&#x60;, &#x60;list_memberships&#x60;, &#x60;phone_numbers&#x60;, &#x60;street_addresses&#x60;, &#x60;notes&#x60;, and &#x60;taggings&#x60;.
     # @return [Array<(GetContactById200Response, Integer, Hash)>] GetContactById200Response data, response status code and response headers
     def get_contact_by_id_with_http_info(contact_id, opts = {})
       if @api_client.config.debugging
@@ -599,8 +599,80 @@ module ConstantContactClient
       return data, status_code, headers
     end
 
+    # PUT Resubscribe a Contact
+    # Use this endpoint to send a confirmation resubscribe email to a contact in order to get their confirmation to resubscribe. This endpoint also adds the resubscribed contact to the contact lists you specify in the request body. You can only send a resubscribe email to the unsubscribed contact once. The contact is not resubscribed until after you receive their confirmation. 
+    # @param contact_id [String] The ID that uniquely identifies the contact to resubscribe.
+    # @param resubscribe_contact_request [ResubscribeContactRequest] The JSON payload used to specify one (or more) contact lists to which the contact requested to be resubscribed.
+    # @param [Hash] opts the optional parameters
+    # @return [nil]
+    def resubscribe_contact(contact_id, resubscribe_contact_request, opts = {})
+      resubscribe_contact_with_http_info(contact_id, resubscribe_contact_request, opts)
+      nil
+    end
+
+    # PUT Resubscribe a Contact
+    # Use this endpoint to send a confirmation resubscribe email to a contact in order to get their confirmation to resubscribe. This endpoint also adds the resubscribed contact to the contact lists you specify in the request body. You can only send a resubscribe email to the unsubscribed contact once. The contact is not resubscribed until after you receive their confirmation. 
+    # @param contact_id [String] The ID that uniquely identifies the contact to resubscribe.
+    # @param resubscribe_contact_request [ResubscribeContactRequest] The JSON payload used to specify one (or more) contact lists to which the contact requested to be resubscribed.
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
+    def resubscribe_contact_with_http_info(contact_id, resubscribe_contact_request, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: ContactsApi.resubscribe_contact ...'
+      end
+      # verify the required parameter 'contact_id' is set
+      if @api_client.config.client_side_validation && contact_id.nil?
+        fail ArgumentError, "Missing the required parameter 'contact_id' when calling ContactsApi.resubscribe_contact"
+      end
+      # verify the required parameter 'resubscribe_contact_request' is set
+      if @api_client.config.client_side_validation && resubscribe_contact_request.nil?
+        fail ArgumentError, "Missing the required parameter 'resubscribe_contact_request' when calling ContactsApi.resubscribe_contact"
+      end
+      # resource path
+      local_var_path = '/contacts/resubscribe/{contact_id}'.sub('{' + 'contact_id' + '}', CGI.escape(contact_id.to_s))
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Content-Type'
+      content_type = @api_client.select_header_content_type(['application/json'])
+      if !content_type.nil?
+          header_params['Content-Type'] = content_type
+      end
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(resubscribe_contact_request)
+
+      # return_type
+      return_type = opts[:debug_return_type]
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['oauth2_access_code', 'oauth2_implicit']
+
+      new_options = opts.merge(
+        :operation => :"ContactsApi.resubscribe_contact",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:PUT, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: ContactsApi#resubscribe_contact\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # PUT (update) a Contact
-    # The PUT method updates an existing contact. You must include the `update_source` property in the PUT request payload. To restore  a deleted contact you must specify the `update_source` as `Account`. When updating any resource using PUT, all properties are updated, overwriting all previous values. Any properties left blank or not included in the request are overwritten with null value - however this does not apply to contact subresources. Add or change any of the subresources by including them in the PUT request payload. Omitted subresources are not overwritten with null. If the contact being updated is deleted, the contact will be revived.
+    # The PUT method updates an existing contact. You must include the `update_source` property in the PUT request payload. To restore  a deleted contact you must specify the `update_source` as `Account`. When updating any resource using PUT, all properties are updated, overwriting all previous values. Any properties left blank or not included in the request are overwritten with null value - however this does not apply to contact subresources.   Add or change any of the subresources by including them in the PUT request payload. Omitted subresources are not overwritten with null. If the contact being updated is deleted, the contact will be revived. If `email_address` is specified: <div class=\"Msg\"><p class=\"note-text\"> **Only use this method when a contact gives you their explicit permission to send them an email. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.</p></div>  If `sms_channel` is specified: <div class=\"Msg\"><p class=\"note-text\">Only use this method when a contact gives you their explicit permission to send them an SMS. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.</p></div>
     # @param contact_id [String] Unique ID of contact to update
     # @param update_contact_request [UpdateContactRequest] JSON payload defining the contact object, with updates. Any properties left blank or not included in the PUT payload are overwritten with null value - does not apply to contact subresources.
     # @param [Hash] opts the optional parameters
@@ -611,7 +683,7 @@ module ConstantContactClient
     end
 
     # PUT (update) a Contact
-    # The PUT method updates an existing contact. You must include the &#x60;update_source&#x60; property in the PUT request payload. To restore  a deleted contact you must specify the &#x60;update_source&#x60; as &#x60;Account&#x60;. When updating any resource using PUT, all properties are updated, overwriting all previous values. Any properties left blank or not included in the request are overwritten with null value - however this does not apply to contact subresources. Add or change any of the subresources by including them in the PUT request payload. Omitted subresources are not overwritten with null. If the contact being updated is deleted, the contact will be revived.
+    # The PUT method updates an existing contact. You must include the &#x60;update_source&#x60; property in the PUT request payload. To restore  a deleted contact you must specify the &#x60;update_source&#x60; as &#x60;Account&#x60;. When updating any resource using PUT, all properties are updated, overwriting all previous values. Any properties left blank or not included in the request are overwritten with null value - however this does not apply to contact subresources.   Add or change any of the subresources by including them in the PUT request payload. Omitted subresources are not overwritten with null. If the contact being updated is deleted, the contact will be revived. If &#x60;email_address&#x60; is specified: &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt; **Only use this method when a contact gives you their explicit permission to send them an email. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.&lt;/p&gt;&lt;/div&gt;  If &#x60;sms_channel&#x60; is specified: &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt;Only use this method when a contact gives you their explicit permission to send them an SMS. It is a violation of anti-spam and telemarketing laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.&lt;/p&gt;&lt;/div&gt;
     # @param contact_id [String] Unique ID of contact to update
     # @param update_contact_request [UpdateContactRequest] JSON payload defining the contact object, with updates. Any properties left blank or not included in the PUT payload are overwritten with null value - does not apply to contact subresources.
     # @param [Hash] opts the optional parameters

data/lib/constant_contact_client/api/contacts_custom_fields_api.rb

@@ -1,9 +1,9 @@
 =begin
 #Constant Contact API v3
 
-#Swagger build version 3.0.2475
+#Swagger build version 3.0.161
 
-The version of the OpenAPI document: 1.0.101
+The version of the OpenAPI document: 1.0.220
 Contact: webservices@constantcontact.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.2.0
@@ -20,27 +20,27 @@ module ConstantContactClient
       @api_client = api_client
     end
     # POST (create) a custom_field
-    # This POST request adds a new `custom_field` to the user's account. A user can configure up to 100 `custom_fields` in their account.
-    # @param update_custom_field_request [UpdateCustomFieldRequest] The JSON payload required to create a new `custom_field`
+    # Custom fields are extra data fields you create to store additional information about your contacts, such as preferences, membership levels, and interests. Use custom fields to organize contacts, send personalized email campaigns, and to identify a targeted audience for a specific campaign. Custom fields types include text, number, date, drop-down lists, radio buttons, and checkboxes. A user can configure up to 100 `custom_fields` in their account.
+    # @param create_custom_fields_request [CreateCustomFieldsRequest] The JSON payload required to create a new custom field.
     # @param [Hash] opts the optional parameters
     # @return [GetCustomField200Response]
-    def create_custom_fields(update_custom_field_request, opts = {})
-      data, _status_code, _headers = create_custom_fields_with_http_info(update_custom_field_request, opts)
+    def create_custom_fields(create_custom_fields_request, opts = {})
+      data, _status_code, _headers = create_custom_fields_with_http_info(create_custom_fields_request, opts)
       data
     end
 
     # POST (create) a custom_field
-    # This POST request adds a new `custom_field` to the user's account. A user can configure up to 100 `custom_fields` in their account.
-    # @param update_custom_field_request [UpdateCustomFieldRequest] The JSON payload required to create a new `custom_field`
+    # Custom fields are extra data fields you create to store additional information about your contacts, such as preferences, membership levels, and interests. Use custom fields to organize contacts, send personalized email campaigns, and to identify a targeted audience for a specific campaign. Custom fields types include text, number, date, drop-down lists, radio buttons, and checkboxes. A user can configure up to 100 `custom_fields` in their account.
+    # @param create_custom_fields_request [CreateCustomFieldsRequest] The JSON payload required to create a new custom field.
     # @param [Hash] opts the optional parameters
     # @return [Array<(GetCustomField200Response, Integer, Hash)>] GetCustomField200Response data, response status code and response headers
-    def create_custom_fields_with_http_info(update_custom_field_request, opts = {})
+    def create_custom_fields_with_http_info(create_custom_fields_request, opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: ContactsCustomFieldsApi.create_custom_fields ...'
       end
-      # verify the required parameter 'update_custom_field_request' is set
-      if @api_client.config.client_side_validation && update_custom_field_request.nil?
-        fail ArgumentError, "Missing the required parameter 'update_custom_field_request' when calling ContactsCustomFieldsApi.create_custom_fields"
+      # verify the required parameter 'create_custom_fields_request' is set
+      if @api_client.config.client_side_validation && create_custom_fields_request.nil?
+        fail ArgumentError, "Missing the required parameter 'create_custom_fields_request' when calling ContactsCustomFieldsApi.create_custom_fields"
       end
       # resource path
       local_var_path = '/contact_custom_fields'
@@ -62,7 +62,7 @@ module ConstantContactClient
       form_params = opts[:form_params] || {}
 
       # http body (model)
-      post_body = opts[:debug_body] || @api_client.object_to_http_body(update_custom_field_request)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(create_custom_fields_request)
 
       # return_type
       return_type = opts[:debug_return_type] || 'GetCustomField200Response'
@@ -88,8 +88,8 @@ module ConstantContactClient
     end
 
     # DELETE a custom_field
-    # This DELETE request deletes a custom_field from the user's account
-    # @param custom_field_id [String] Unique ID of the custom_field on which to operate.
+    # Delete a custom field from the user's account.
+    # @param custom_field_id [String] The ID that uniquely identifies the custom field to delete.
     # @param [Hash] opts the optional parameters
     # @return [nil]
     def delete_custom_field(custom_field_id, opts = {})
@@ -98,8 +98,8 @@ module ConstantContactClient
     end
 
     # DELETE a custom_field
-    # This DELETE request deletes a custom_field from the user&#39;s account
-    # @param custom_field_id [String] Unique ID of the custom_field on which to operate.
+    # Delete a custom field from the user&#39;s account.
+    # @param custom_field_id [String] The ID that uniquely identifies the custom field to delete.
     # @param [Hash] opts the optional parameters
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
     def delete_custom_field_with_http_info(custom_field_id, opts = {})
@@ -149,7 +149,7 @@ module ConstantContactClient
     end
 
     # GET custom_fields Collection
-    # This GET request returns all `custom_fields` defined in the user's account. <div class=\"Msg\"><p class=\"note-text\">This method does not currently support filtering results using the custom field update date.</p></div>
+    # Get all custom fields defined in the user's account. <div class=\"Msg\"><p class=\"note-text\">This method does not currently support filtering results using the custom field update date.</p></div>
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :limit Specifies the number of results displayed per page of output, from 1 - 100, default &#x3D; 50. (default to 50)
     # @return [GetAllCustomFields200Response]
@@ -159,7 +159,7 @@ module ConstantContactClient
     end
 
     # GET custom_fields Collection
-    # This GET request returns all &#x60;custom_fields&#x60; defined in the user&#39;s account. &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt;This method does not currently support filtering results using the custom field update date.&lt;/p&gt;&lt;/div&gt;
+    # Get all custom fields defined in the user&#39;s account. &lt;div class&#x3D;\&quot;Msg\&quot;&gt;&lt;p class&#x3D;\&quot;note-text\&quot;&gt;This method does not currently support filtering results using the custom field update date.&lt;/p&gt;&lt;/div&gt;
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :limit Specifies the number of results displayed per page of output, from 1 - 100, default &#x3D; 50. (default to 50)
     # @return [Array<(GetAllCustomFields200Response, Integer, Hash)>] GetAllCustomFields200Response data, response status code and response headers
@@ -217,8 +217,8 @@ module ConstantContactClient
     end
 
     # GET a custom_field
-    # This GET call retrieves a `custom_field` resource, specified by `custom_field_id`.
-    # @param custom_field_id [String] Unique ID of the &#x60;custom_field&#x60; on which to operate.
+    # Get details for a specified custom field.
+    # @param custom_field_id [String] The ID that uniquely identifies the custom field.
     # @param [Hash] opts the optional parameters
     # @return [GetCustomField200Response]
     def get_custom_field(custom_field_id, opts = {})
@@ -227,8 +227,8 @@ module ConstantContactClient
     end
 
     # GET a custom_field
-    # This GET call retrieves a &#x60;custom_field&#x60; resource, specified by &#x60;custom_field_id&#x60;.
-    # @param custom_field_id [String] Unique ID of the &#x60;custom_field&#x60; on which to operate.
+    # Get details for a specified custom field.
+    # @param custom_field_id [String] The ID that uniquely identifies the custom field.
     # @param [Hash] opts the optional parameters
     # @return [Array<(GetCustomField200Response, Integer, Hash)>] GetCustomField200Response data, response status code and response headers
     def get_custom_field_with_http_info(custom_field_id, opts = {})
@@ -279,9 +279,9 @@ module ConstantContactClient
       return data, status_code, headers
     end
 
-    # PUT (update) a custom_field
-    # This PUT request updates an existing `custom_field` object.
-    # @param custom_field_id [String] Unique ID of the &#x60;custom_field&#x60; on which to operate.
+    # Update a custom field.
+    # Update an existing custom field.
+    # @param custom_field_id [String] The ID that uniquely identifies the custom field to update.
     # @param update_custom_field_request [UpdateCustomFieldRequest] The JSON payload used to update an existing custom field. Any properties omitted in the PUT request are overwritten with a null value.
     # @param [Hash] opts the optional parameters
     # @return [GetCustomField200Response]
@@ -290,9 +290,9 @@ module ConstantContactClient
       data
     end
 
-    # PUT (update) a custom_field
-    # This PUT request updates an existing &#x60;custom_field&#x60; object.
-    # @param custom_field_id [String] Unique ID of the &#x60;custom_field&#x60; on which to operate.
+    # Update a custom field.
+    # Update an existing custom field.
+    # @param custom_field_id [String] The ID that uniquely identifies the custom field to update.
     # @param update_custom_field_request [UpdateCustomFieldRequest] The JSON payload used to update an existing custom field. Any properties omitted in the PUT request are overwritten with a null value.
     # @param [Hash] opts the optional parameters
     # @return [Array<(GetCustomField200Response, Integer, Hash)>] GetCustomField200Response data, response status code and response headers

data/lib/constant_contact_client/api/contacts_reporting_api.rb

@@ -1,9 +1,9 @@
 =begin
 #Constant Contact API v3
 
-#Swagger build version 3.0.2475
+#Swagger build version 3.0.161
 
-The version of the OpenAPI document: 1.0.101
+The version of the OpenAPI document: 1.0.220
 Contact: webservices@constantcontact.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.2.0

data/lib/constant_contact_client/api/email_campaigns_ab_tests_api.rb

@@ -1,9 +1,9 @@
 =begin
 #Constant Contact API v3
 
-#Swagger build version 3.0.2475
+#Swagger build version 3.0.161
 
-The version of the OpenAPI document: 1.0.101
+The version of the OpenAPI document: 1.0.220
 Contact: webservices@constantcontact.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.2.0

data/lib/constant_contact_client/api/email_campaigns_api.rb

@@ -1,9 +1,9 @@
 =begin
 #Constant Contact API v3
 
-#Swagger build version 3.0.2475
+#Swagger build version 3.0.161
 
-The version of the OpenAPI document: 1.0.101
+The version of the OpenAPI document: 1.0.220
 Contact: webservices@constantcontact.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.2.0
@@ -20,7 +20,7 @@ module ConstantContactClient
       @api_client = api_client
     end
     # POST (Create) a New Email Campaign
-    # Use this method to create a new email campaign. This method also creates new `primary_email` and `permalink` email campaign activities and associates them with the new email campaign.  The request body must contain the `name` property and the `email_campaign_activities` array. The `name` must be unique. The `email_campaign_activities` array contains the main content of your email campaign and must include `format_type`, `from_name`, `from_email`, `reply_to_email`, `subject`, and `html_content` properties. The `from_email` address you use must use a verified email address for your account. NOTE: If you create an email campaign using a legacy (V7) format, Constant Contact automatically converts it to the newer custom code format. 
+    # Use this method to create a new email campaign. You must include a tracking image (`[[trackingImage]]`) in the email body in order for Constant Contact to report on the email performance. This method also creates new `primary_email` and `permalink` email campaign activities and associates them with the new email campaign. The request body must contain the `name` property and the `email_campaign_activities` array. The `name` must be unique. The `email_campaign_activities` array contains the main content of your email campaign and must include `format_type`, `from_name`, `from_email`, `reply_to_email`, `subject`, and `html_content` properties. The `from_email` address you use must use a verified email address for your account. NOTE: If you create an email campaign using a legacy (V7) format, Constant Contact automatically converts it to the newer custom code format. 
     # @param create_email_campaign_request [CreateEmailCampaignRequest] A JSON request body that contains the email content.
     # @param [Hash] opts the optional parameters
     # @return [CreateEmailCampaign200Response]
@@ -30,7 +30,7 @@ module ConstantContactClient
     end
 
     # POST (Create) a New Email Campaign
-    # Use this method to create a new email campaign. This method also creates new `primary_email` and `permalink` email campaign activities and associates them with the new email campaign.  The request body must contain the `name` property and the `email_campaign_activities` array. The `name` must be unique. The `email_campaign_activities` array contains the main content of your email campaign and must include `format_type`, `from_name`, `from_email`, `reply_to_email`, `subject`, and `html_content` properties. The `from_email` address you use must use a verified email address for your account. NOTE: If you create an email campaign using a legacy (V7) format, Constant Contact automatically converts it to the newer custom code format. 
+    # Use this method to create a new email campaign. You must include a tracking image (`[[trackingImage]]`) in the email body in order for Constant Contact to report on the email performance. This method also creates new `primary_email` and `permalink` email campaign activities and associates them with the new email campaign. The request body must contain the `name` property and the `email_campaign_activities` array. The `name` must be unique. The `email_campaign_activities` array contains the main content of your email campaign and must include `format_type`, `from_name`, `from_email`, `reply_to_email`, `subject`, and `html_content` properties. The `from_email` address you use must use a verified email address for your account. NOTE: If you create an email campaign using a legacy (V7) format, Constant Contact automatically converts it to the newer custom code format. 
     # @param create_email_campaign_request [CreateEmailCampaignRequest] A JSON request body that contains the email content.
     # @param [Hash] opts the optional parameters
     # @return [Array<(CreateEmailCampaign200Response, Integer, Hash)>] CreateEmailCampaign200Response data, response status code and response headers

data/lib/constant_contact_client/api/email_reporting_api.rb

@@ -1,9 +1,9 @@
 =begin
 #Constant Contact API v3
 
-#Swagger build version 3.0.2475
+#Swagger build version 3.0.161
 
-The version of the OpenAPI document: 1.0.101
+The version of the OpenAPI document: 1.0.220
 Contact: webservices@constantcontact.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.2.0

data/lib/constant_contact_client/api/email_scheduling_api.rb

@@ -1,9 +1,9 @@
 =begin
 #Constant Contact API v3
 
-#Swagger build version 3.0.2475
+#Swagger build version 3.0.161
 
-The version of the OpenAPI document: 1.0.101
+The version of the OpenAPI document: 1.0.220
 Contact: webservices@constantcontact.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.2.0
@@ -209,7 +209,7 @@ module ConstantContactClient
     end
 
     # POST (Create) an Email Campaign Activity Schedule
-    # Use this method to schedule when Constant Contact will send an email campaign activity to contacts. Use the `scheduled_date` request body property to enter the ISO-8601 format date that you want Constant Contact to send the email campaign activity on.   Before you schedule an email campaign activity, you must update the email campaign activity and specify which contacts you want Constant Contact to send the email to. When you make a PUT call to update an email campaign activity, use the `contact_list_ids` or `segment_ids` array to add contacts.  You can only schedule email campaign activities that have the `primary_email` role and are in `DRAFT`, `DONE`, or `ERROR` status. When you schedule an email campaign activity in `DONE` status, Constant Contact does not send the email campaign activity to contacts that already received it. Constant Contact only sends the email campaign activity to any new contacts in the contact lists or segment you use. 
+    # Use this method to send an email campaign activity to contacts either immediately or on a specific date. To send the email campaign activity immediately, specify `0` for the `scheduled_date` request property (results return an empty array). To send the email campaign activity on a specific date, specify the date using the `scheduled_date` request property (results return the scheduled date in an array).    Before you schedule an email campaign activity, you must update the email campaign activity and specify which contacts you want Constant Contact to send the email to. When you make a PUT call to update an email campaign activity, use the `contact_list_ids` or `segment_ids` array to add contacts.  You can only schedule email campaign activities that have the `primary_email` role and are in `DRAFT`, `DONE`, or `ERROR` status. When you schedule an email campaign activity in `DONE` status, Constant Contact does not send the email campaign activity to contacts that already received it. Constant Contact only sends the email campaign activity to any new contacts in the contact lists or segment you use. 
     # @param campaign_activity_id [String] The unique ID for an email campaign activity. You can only schedule email campaign activities that have the `primary_email` role.
     # @param schedule_email_campaign_activity_request [ScheduleEmailCampaignActivityRequest] A request body payload that contains the date that you want Constant Contact to send your email campaign activity on. Use `\"0\"` as the date to have Constant Contact immediately send the email campaign activity.
     # @param [Hash] opts the optional parameters
@@ -220,7 +220,7 @@ module ConstantContactClient
     end
 
     # POST (Create) an Email Campaign Activity Schedule
-    # Use this method to schedule when Constant Contact will send an email campaign activity to contacts. Use the `scheduled_date` request body property to enter the ISO-8601 format date that you want Constant Contact to send the email campaign activity on.   Before you schedule an email campaign activity, you must update the email campaign activity and specify which contacts you want Constant Contact to send the email to. When you make a PUT call to update an email campaign activity, use the `contact_list_ids` or `segment_ids` array to add contacts.  You can only schedule email campaign activities that have the `primary_email` role and are in `DRAFT`, `DONE`, or `ERROR` status. When you schedule an email campaign activity in `DONE` status, Constant Contact does not send the email campaign activity to contacts that already received it. Constant Contact only sends the email campaign activity to any new contacts in the contact lists or segment you use. 
+    # Use this method to send an email campaign activity to contacts either immediately or on a specific date. To send the email campaign activity immediately, specify `0` for the `scheduled_date` request property (results return an empty array). To send the email campaign activity on a specific date, specify the date using the `scheduled_date` request property (results return the scheduled date in an array).    Before you schedule an email campaign activity, you must update the email campaign activity and specify which contacts you want Constant Contact to send the email to. When you make a PUT call to update an email campaign activity, use the `contact_list_ids` or `segment_ids` array to add contacts.  You can only schedule email campaign activities that have the `primary_email` role and are in `DRAFT`, `DONE`, or `ERROR` status. When you schedule an email campaign activity in `DONE` status, Constant Contact does not send the email campaign activity to contacts that already received it. Constant Contact only sends the email campaign activity to any new contacts in the contact lists or segment you use. 
     # @param campaign_activity_id [String] The unique ID for an email campaign activity. You can only schedule email campaign activities that have the `primary_email` role.
     # @param schedule_email_campaign_activity_request [ScheduleEmailCampaignActivityRequest] A request body payload that contains the date that you want Constant Contact to send your email campaign activity on. Use `\"0\"` as the date to have Constant Contact immediately send the email campaign activity.
     # @param [Hash] opts the optional parameters