constant_contact_client 1.0.0 → 1.5.0

data/Gemfile.lock

@@ -1,49 +1,68 @@
 PATH
   remote: .
   specs:
-    constant_contact_client (1.0.0)
+    constant_contact_client (1.5.0)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    ast (2.4.2)
-    byebug (11.1.3)
+    ast (2.4.3)
+    byebug (13.0.0)
+      reline (>= 0.6.0)
     coderay (1.1.3)
-    diff-lcs (1.5.1)
-    ethon (0.16.0)
+    date (3.5.1)
+    diff-lcs (1.6.2)
+    ethon (0.18.0)
       ffi (>= 1.15.0)
-    ffi (1.17.0-x86_64-linux-gnu)
+      logger
+    ffi (1.17.4)
+    ffi (1.17.4-aarch64-linux-gnu)
+    ffi (1.17.4-aarch64-linux-musl)
+    ffi (1.17.4-arm-linux-gnu)
+    ffi (1.17.4-arm-linux-musl)
+    ffi (1.17.4-arm64-darwin)
+    ffi (1.17.4-x86-linux-gnu)
+    ffi (1.17.4-x86-linux-musl)
+    ffi (1.17.4-x86_64-darwin)
+    ffi (1.17.4-x86_64-linux-gnu)
+    ffi (1.17.4-x86_64-linux-musl)
+    io-console (0.8.2)
     jaro_winkler (1.5.6)
+    logger (1.7.0)
     method_source (1.1.0)
-    parallel (1.26.3)
-    parser (3.3.5.0)
+    parallel (1.28.0)
+    parser (3.3.11.1)
       ast (~> 2.4.1)
       racc
-    pry (0.14.2)
+    pry (0.16.0)
       coderay (~> 1.1)
       method_source (~> 1.0)
-    pry-byebug (3.10.1)
-      byebug (~> 11.0)
-      pry (>= 0.13, < 0.15)
-    psych (5.1.2)
+      reline (>= 0.6.0)
+    pry-byebug (3.12.0)
+      byebug (~> 13.0)
+      pry (>= 0.13, < 0.17)
+    psych (5.4.0)
+      date
       stringio
     racc (1.8.1)
     rainbow (3.1.1)
     rake (13.0.6)
-    rspec (3.13.0)
+    reline (0.6.3)
+      io-console (~> 0.5)
+    rspec (3.13.2)
       rspec-core (~> 3.13.0)
       rspec-expectations (~> 3.13.0)
       rspec-mocks (~> 3.13.0)
-    rspec-core (3.13.1)
+    rspec-core (3.13.6)
       rspec-support (~> 3.13.0)
-    rspec-expectations (3.13.3)
+    rspec-expectations (3.13.5)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
-    rspec-mocks (3.13.2)
+    rspec-mocks (3.13.8)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
-    rspec-support (3.13.1)
+    rspec-support (3.13.7)
     rubocop (0.66.0)
       jaro_winkler (~> 1.5.1)
       parallel (~> 1.10)
@@ -53,13 +72,23 @@ GEM
       ruby-progressbar (~> 1.7)
       unicode-display_width (>= 1.4.0, < 1.6)
     ruby-progressbar (1.13.0)
-    stringio (3.1.1)
-    typhoeus (1.4.1)
-      ethon (>= 0.9.0)
+    stringio (3.2.0)
+    typhoeus (1.6.0)
+      ethon (>= 0.18.0)
     unicode-display_width (1.5.0)
 
 PLATFORMS
-  x86_64-linux
+  aarch64-linux-gnu
+  aarch64-linux-musl
+  arm-linux-gnu
+  arm-linux-musl
+  arm64-darwin
+  ruby
+  x86-linux-gnu
+  x86-linux-musl
+  x86_64-darwin
+  x86_64-linux-gnu
+  x86_64-linux-musl
 
 DEPENDENCIES
   constant_contact_client!
@@ -69,4 +98,4 @@ DEPENDENCIES
   rubocop (~> 0.66.0)
 
 BUNDLED WITH
-   2.3.27
+   2.5.21

data/README.md

@@ -2,12 +2,12 @@
 
 ConstantContactClient - the Ruby gem for the Constant Contact API v3
 
-Swagger build version 3.0.2475
+Swagger build version 3.0.161
 
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: 1.0.101
-- Package version: 1.0.0
+- API version: 1.0.220
+- Package version: 1.5.0
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
 ## Installation
@@ -23,11 +23,11 @@ gem build constant_contact_client.gemspec
 Then either install the gem locally:
 
 ```shell
-gem install ./constant_contact_client-1.0.0.gem
+gem install ./constant_contact_client-1.5.0.gem
 ```
 Finally add this to the Gemfile:
 
-    gem 'constant_contact_client', '~> 1.0.0'
+    gem 'constant_contact_client', '~> 1.5.0'
 
 Or install from rubygems:
 ```shell
@@ -145,12 +145,13 @@ Class | Method | HTTP request | Description
 *ConstantContactClient::ContactsApi* | [**get_contact_counts**](docs/ContactsApi.md#get_contact_counts) | **GET** /contacts/counts | GET Contact Consent Counts
 *ConstantContactClient::ContactsApi* | [**get_contact_id_xrefs**](docs/ContactsApi.md#get_contact_id_xrefs) | **GET** /contacts/contact_id_xrefs | GET a collection of V2 and V3 API contact IDs
 *ConstantContactClient::ContactsApi* | [**get_sms_engagement_history**](docs/ContactsApi.md#get_sms_engagement_history) | **GET** /contacts/sms_engagement_history/{contact_id} | GET SMS Engagement History for a Contact
+*ConstantContactClient::ContactsApi* | [**resubscribe_contact**](docs/ContactsApi.md#resubscribe_contact) | **PUT** /contacts/resubscribe/{contact_id} | PUT Resubscribe a Contact
 *ConstantContactClient::ContactsApi* | [**update_contact**](docs/ContactsApi.md#update_contact) | **PUT** /contacts/{contact_id} | PUT (update) a Contact
 *ConstantContactClient::ContactsCustomFieldsApi* | [**create_custom_fields**](docs/ContactsCustomFieldsApi.md#create_custom_fields) | **POST** /contact_custom_fields | POST (create) a custom_field
 *ConstantContactClient::ContactsCustomFieldsApi* | [**delete_custom_field**](docs/ContactsCustomFieldsApi.md#delete_custom_field) | **DELETE** /contact_custom_fields/{custom_field_id} | DELETE a custom_field
 *ConstantContactClient::ContactsCustomFieldsApi* | [**get_all_custom_fields**](docs/ContactsCustomFieldsApi.md#get_all_custom_fields) | **GET** /contact_custom_fields | GET custom_fields Collection
 *ConstantContactClient::ContactsCustomFieldsApi* | [**get_custom_field**](docs/ContactsCustomFieldsApi.md#get_custom_field) | **GET** /contact_custom_fields/{custom_field_id} | GET a custom_field
-*ConstantContactClient::ContactsCustomFieldsApi* | [**update_custom_field**](docs/ContactsCustomFieldsApi.md#update_custom_field) | **PUT** /contact_custom_fields/{custom_field_id} | PUT (update) a custom_field
+*ConstantContactClient::ContactsCustomFieldsApi* | [**update_custom_field**](docs/ContactsCustomFieldsApi.md#update_custom_field) | **PUT** /contact_custom_fields/{custom_field_id} | Update a custom field.
 *ConstantContactClient::ContactsReportingApi* | [**get_contact_open_click_rate_report**](docs/ContactsReportingApi.md#get_contact_open_click_rate_report) | **GET** /reports/contact_reports/{contact_id}/open_and_click_rates | GET Average Open and Click Rates
 *ConstantContactClient::ContactsReportingApi* | [**get_contact_tracking_count_report**](docs/ContactsReportingApi.md#get_contact_tracking_count_report) | **GET** /reports/contact_reports/{contact_id}/activity_summary | GET Contact Action Summary
 *ConstantContactClient::ContactsReportingApi* | [**get_contact_tracking_report**](docs/ContactsReportingApi.md#get_contact_tracking_report) | **GET** /reports/contact_reports/{contact_id}/activity_details | GET Contact Activity Details
@@ -186,16 +187,32 @@ Class | Method | HTTP request | Description
 *ConstantContactClient::EmailSchedulingApi* | [**schedule_email_campaign_activity**](docs/EmailSchedulingApi.md#schedule_email_campaign_activity) | **POST** /emails/activities/{campaign_activity_id}/schedules | POST (Create) an Email Campaign Activity Schedule
 *ConstantContactClient::EmailSchedulingApi* | [**test_send_email_campaign_activity**](docs/EmailSchedulingApi.md#test_send_email_campaign_activity) | **POST** /emails/activities/{campaign_activity_id}/tests | POST Test Send an Email Campaign Activity
 *ConstantContactClient::EmailSchedulingApi* | [**unschedule_email_campaign_activity**](docs/EmailSchedulingApi.md#unschedule_email_campaign_activity) | **DELETE** /emails/activities/{campaign_activity_id}/schedules | DELETE an Email Campaign Activity Schedule
+*ConstantContactClient::EventsApi* | [**check_in_tickets**](docs/EventsApi.md#check_in_tickets) | **POST** /events/{event_id}/check_in/tickets | Check in event tickets.
+*ConstantContactClient::EventsApi* | [**copy_event**](docs/EventsApi.md#copy_event) | **POST** /events/{event_id}/copy | POST (copy) an existing event.
+*ConstantContactClient::EventsApi* | [**create_event**](docs/EventsApi.md#create_event) | **POST** /events/default | POST (create) a new event.
+*ConstantContactClient::EventsApi* | [**find_events**](docs/EventsApi.md#find_events) | **GET** /events | GET a collection of events.
+*ConstantContactClient::EventsApi* | [**find_registrations_using_get**](docs/EventsApi.md#find_registrations_using_get) | **GET** /events/{event_id}/tracks/{track_id}/registrations | Get a list of registrations for an event.
+*ConstantContactClient::EventsApi* | [**get_event2**](docs/EventsApi.md#get_event2) | **GET** /events/{event_id} | GET details for a single event.
+*ConstantContactClient::EventsApi* | [**get_registration_info**](docs/EventsApi.md#get_registration_info) | **GET** /events/{event_id}/tracks/{track_id}/registrations/{registration_id} | Get registration details for an event.
+*ConstantContactClient::EventsApi* | [**undo_check_in_tickets**](docs/EventsApi.md#undo_check_in_tickets) | **POST** /events/{event_id}/undo_check_in/tickets | Undo event ticket check-in.
+*ConstantContactClient::EventsApi* | [**update_event**](docs/EventsApi.md#update_event) | **PATCH** /events/{event_id} | PATCH (update) an event.
+*ConstantContactClient::EventsApi* | [**update_registration_payment_status_using_put**](docs/EventsApi.md#update_registration_payment_status_using_put) | **PUT** /events/{event_id}/tracks/{track_id}/registrations/payment_status | Update payment status for event registrations.
+*ConstantContactClient::EventsApi* | [**update_registration_status_using_put**](docs/EventsApi.md#update_registration_status_using_put) | **PUT** /events/{event_id}/tracks/{track_id}/registrations | Update status for event registrations.
 *ConstantContactClient::LandingPagesReportingApi* | [**get_contact_adds**](docs/LandingPagesReportingApi.md#get_contact_adds) | **GET** /reports/landing_pages/campaign_details/{campaign_activity_id}/p_unique_contact_adds | GET a Unique Contacts Adds Landing Page Report
 *ConstantContactClient::LandingPagesReportingApi* | [**get_contact_opens**](docs/LandingPagesReportingApi.md#get_contact_opens) | **GET** /reports/landing_pages/campaign_details/{campaign_activity_id}/p_contact_opens | GET a Contacts Opens Landing Page Report
 *ConstantContactClient::LandingPagesReportingApi* | [**get_unique_contact_clicks**](docs/LandingPagesReportingApi.md#get_unique_contact_clicks) | **GET** /reports/landing_pages/campaign_details/{campaign_activity_id}/p_unique_contact_clicks | GET a Unique Contacts Clicks Landing Page Report
 *ConstantContactClient::LandingPagesReportingApi* | [**get_unique_contact_opens**](docs/LandingPagesReportingApi.md#get_unique_contact_opens) | **GET** /reports/landing_pages/campaign_details/{campaign_activity_id}/p_unique_contact_opens | GET a Unique Contacts Opens Landing Page Report
 *ConstantContactClient::LandingPagesReportingApi* | [**get_unique_contact_sms_opt_ins**](docs/LandingPagesReportingApi.md#get_unique_contact_sms_opt_ins) | **GET** /reports/landing_pages/campaign_details/{campaign_activity_id}/p_unique_contact_sms_optins | GET a Unique Contacts SMS Opt-In Landing Page Report
 *ConstantContactClient::LandingPagesReportingApi* | [**get_unique_contact_updates**](docs/LandingPagesReportingApi.md#get_unique_contact_updates) | **GET** /reports/landing_pages/campaign_details/{campaign_activity_id}/p_unique_contact_updates | GET a Unique Contacts Updates Landing Page Report
+*ConstantContactClient::SMSReportingApi* | [**get_all_bulk_sms_campaign_summaries**](docs/SMSReportingApi.md#get_all_bulk_sms_campaign_summaries) | **GET** /reports/summary_reports/sms_campaign_summaries | GET an SMS Campaigns Summary Report
 *ConstantContactClient::SegmentsApi* | [**create_segment**](docs/SegmentsApi.md#create_segment) | **POST** /segments | POST (create) a Segment
 *ConstantContactClient::SegmentsApi* | [**delete_segment**](docs/SegmentsApi.md#delete_segment) | **DELETE** /segments/{segment_id} | DELETE a Segment
 *ConstantContactClient::SegmentsApi* | [**get_all_segments**](docs/SegmentsApi.md#get_all_segments) | **GET** /segments | GET all Segments
 *ConstantContactClient::SegmentsApi* | [**get_segment_by_id**](docs/SegmentsApi.md#get_segment_by_id) | **GET** /segments/{segment_id} | GET a Segment's Details
 *ConstantContactClient::SegmentsApi* | [**update_segment**](docs/SegmentsApi.md#update_segment) | **PUT** /segments/{segment_id} | PUT (update) a Segment
 *ConstantContactClient::SegmentsApi* | [**update_segment_name**](docs/SegmentsApi.md#update_segment_name) | **PATCH** /segments/{segment_id}/name | PATCH (rename) a Segment
+*ConstantContactClient::SocialApi* | [**create_social_post**](docs/SocialApi.md#create_social_post) | **POST** /social/posts | POST (create) a social media post
+*ConstantContactClient::SocialApi* | [**get_hashtag_groups**](docs/SocialApi.md#get_hashtag_groups) | **GET** /social/hashtags/groups | GET hashtag groups
+*ConstantContactClient::SocialApi* | [**get_social_connections**](docs/SocialApi.md#get_social_connections) | **GET** /social/connections | GET social network connections
+*ConstantContactClient::SocialApi* | [**get_social_profiles**](docs/SocialApi.md#get_social_profiles) | **GET** /social/profiles | GET social media profiles
 

data/constant_contact_client.gemspec

@@ -3,9 +3,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
@@ -23,7 +23,7 @@ Gem::Specification.new do |s|
   s.email       = ["ctct-publicapi@constantcontact.com"]
   s.homepage    = "https://v3.developer.constantcontact.com/"
   s.summary     = "Constant Contact API v3 Ruby Gem"
-  s.description = "Swagger build version 3.0.2475"
+  s.description = "Swagger build version 3.0.161"
   s.license     = "BSD 3-Clause"
   s.required_ruby_version = ">= 2.7"
   s.metadata    = {}

data/docs/AccountServicesApi.md

@@ -109,7 +109,7 @@ ConstantContactClient.configure do |config|
 end
 
 api_instance = ConstantContactClient::AccountServicesApi.new
-get_account_details200_response_physical_address = ConstantContactClient::GetAccountDetails200ResponsePhysicalAddress.new({address_line1: '123 Maple Street', city: 'Boston', country_code: 'US'}) # GetAccountDetails200ResponsePhysicalAddress | Include all `AccountPhysicalAddress` properties required for the specified `country_code` and then update only those properties that you want to change. Excluding a non-read only field from the request body removes it from the physical address.
+get_account_details200_response_physical_address = ConstantContactClient::GetAccountDetails200ResponsePhysicalAddress.new({address_line1: '123 Maple Street', city: 'Boston', country_code: 'US'}) # GetAccountDetails200ResponsePhysicalAddress | Include all `AccountPhysicalAddress` properties required for the specified `country_code`. If a required property is not included or incorrectly formatted, a 400 error message is returned. If the address already exists, a 409 error message is returned.
 
 begin
   # POST the Physical Address for the Account
@@ -142,7 +142,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **get_account_details200_response_physical_address** | [**GetAccountDetails200ResponsePhysicalAddress**](GetAccountDetails200ResponsePhysicalAddress.md) | Include all `AccountPhysicalAddress` properties required for the specified `country_code` and then update only those properties that you want to change. Excluding a non-read only field from the request body removes it from the physical address. |  |
+| **get_account_details200_response_physical_address** | [**GetAccountDetails200ResponsePhysicalAddress**](GetAccountDetails200ResponsePhysicalAddress.md) | Include all `AccountPhysicalAddress` properties required for the specified `country_code`. If a required property is not included or incorrectly formatted, a 400 error message is returned. If the address already exists, a 409 error message is returned. |  |
 
 ### Return type
 

data/docs/BulkActivitiesApi.md

@@ -22,11 +22,11 @@ All URIs are relative to *https://api.cc.email/v3*
 
 ## create_csv_import_activity
 
-> <CreateCSVImportActivity201Response> create_csv_import_activity(file, list_ids)
+> <CreateCSVImportActivity201Response> create_csv_import_activity(file, list_ids, opts)
 
 Import Contacts using a CSV File
 
-This multipart method creates an asynchronous background job that adds or updates contacts by importing a CSV file containing contact information. Do not use a Content-Type header value with this method.  Importing a new contact automatically sets the contact's `permission_to_send` property as `implicit` and the `opt_in_source` property as `Account`. Importing an existing contact only updates the contact properties you include in the request.  The CSV file has a maximum of 40,000 lines including the header row (39,999 contacts) and a maximum file size of 4 megabytes (MB).  Lines above the 40,000 line maximum are not processed. If the request body exceeds 4 MB, only the contacts contained in the first 4 MB are imported and the remaining data is dropped.
+This multipart method creates an asynchronous background job that adds or updates contacts by importing a CSV file containing contact information. Do not use a Content-Type header value with this method.  Importing a new contact email address automatically sets the contact's `permission_to_send` property as `implicit` and the `opt_in_source` property as `Account`. Importing an existing contact only updates the contact properties you include in the request. Importing contacts with `sms_number`s requires using the `sms_permission_to_send` parameter  to specify permissions for all contacts being imported. Set to `explicit` to specify that all contacts either provided explicit permission. Set to `not_set` if permission was not provided. If `explicit`, you must also include the `sms_consent_date` as a column header to include the date the contact consented to receiving SMS messages. Contacts must have either an email address or an SMS number defined.   The CSV file has a maximum of 40,000 lines including the header row (39,999 contacts) and a maximum file size of 4 megabytes (MB).  Lines above the 40,000 line maximum are not processed. If the request body exceeds 4 MB, only the contacts contained in the first 4 MB are imported and the remaining data is dropped.
 
 ### Examples
 
@@ -43,12 +43,15 @@ ConstantContactClient.configure do |config|
 end
 
 api_instance = ConstantContactClient::BulkActivitiesApi.new
-file = File.new('/path/to/some/file') # File | The CSV file you are importing. The column headings that you can use in the file are: `first_name`, `last_name`, `email`, `phone`, `job_title`, `anniversary`, `birthday_day`, `birthday_month`, `company_name`, `street`, `street2`, `city`, `state`, `zip`, and `country`. The only required column heading is `email`.  You can also use custom fields as column headings. Enter the custom field name prefixed with `cf:` as the column heading. For example, use `cf:first_name` as the header name if you have a custom field named \\\"first_name\\\". The custom field must already exist in the Constant Contact account you are using. Depending on the custom field data type, you can enter dates or strings as the value of the custom field. Each contact can contain up to 25 different custom fields.
-list_ids = ['inner_example'] # Array<String> | Specify which contact lists you are adding all imported contacts to as an array of up to 50 contact `list_id` values.
+file = File.new('/path/to/some/file') # File | The CSV file you are importing  must include either `email` or `sms_number` as a column heading. Other properties you can include using column headings are: `first_name`.  `last_name`, `phone`, `job_title`, `anniversary`, `birthday_day`, `birthday_month`, `company_name`, `street`, `street2`, `city`, `state`, `zip`, `country`, and `sms_consent_date`.   If adding an `sms_number`, you must also include the `sms_permission_to_send` parameter and set it to either `not_set` or `explicit`. If `explicit`, requires including `sms_consent_date` as a column header to specify the date the contact consented to receiving SMS messages.   You can also use custom fields as column headings. Enter the custom field name prefixed with `cf:` as the column heading. For example, use `cf:first_name` as the header name if you have a custom field named \\\"first_name\\\". The custom field must already exist in the Constant Contact account you are using. Depending on the custom field data type, you can enter dates or strings as the value of the custom field. Each contact can contain up to 25 different custom fields.
+list_ids = 'list_ids_example' # String | Specify which contact lists you are adding all imported contacts to as an array of up to 50 contact `list_id` values.
+opts = {
+  sms_permission_to_send: 'not_set' # String | If importing contact `sms_number`s, use this parameter to specify how SMS consent was provided. If all contacts in the file provided their consent, set to `explicit` and include each contact's `sms_consent_date`. If all contacts in the file have not yet provided consent, set to `not_set` (`sms_consent_date` is not required). You cannot message a contact that does not have a sms consent date set.
+}
 
 begin
   # Import Contacts using a CSV File
-  result = api_instance.create_csv_import_activity(file, list_ids)
+  result = api_instance.create_csv_import_activity(file, list_ids, opts)
   p result
 rescue ConstantContactClient::ApiError => e
   puts "Error when calling BulkActivitiesApi->create_csv_import_activity: #{e}"
@@ -59,12 +62,12 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<CreateCSVImportActivity201Response>, Integer, Hash)> create_csv_import_activity_with_http_info(file, list_ids)
+> <Array(<CreateCSVImportActivity201Response>, Integer, Hash)> create_csv_import_activity_with_http_info(file, list_ids, opts)
 
 ```ruby
 begin
   # Import Contacts using a CSV File
-  data, status_code, headers = api_instance.create_csv_import_activity_with_http_info(file, list_ids)
+  data, status_code, headers = api_instance.create_csv_import_activity_with_http_info(file, list_ids, opts)
   p status_code # => 2xx
   p headers # => { ... }
   p data # => <CreateCSVImportActivity201Response>
@@ -77,8 +80,9 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **file** | **File** | The CSV file you are importing. The column headings that you can use in the file are: &#x60;first_name&#x60;, &#x60;last_name&#x60;, &#x60;email&#x60;, &#x60;phone&#x60;, &#x60;job_title&#x60;, &#x60;anniversary&#x60;, &#x60;birthday_day&#x60;, &#x60;birthday_month&#x60;, &#x60;company_name&#x60;, &#x60;street&#x60;, &#x60;street2&#x60;, &#x60;city&#x60;, &#x60;state&#x60;, &#x60;zip&#x60;, and &#x60;country&#x60;. The only required column heading is &#x60;email&#x60;.  You can also use custom fields as column headings. Enter the custom field name prefixed with &#x60;cf:&#x60; as the column heading. For example, use &#x60;cf:first_name&#x60; as the header name if you have a custom field named \\\&quot;first_name\\\&quot;. The custom field must already exist in the Constant Contact account you are using. Depending on the custom field data type, you can enter dates or strings as the value of the custom field. Each contact can contain up to 25 different custom fields. |  |
-| **list_ids** | [**Array&lt;String&gt;**](String.md) | Specify which contact lists you are adding all imported contacts to as an array of up to 50 contact &#x60;list_id&#x60; values. |  |
+| **file** | **File** | The CSV file you are importing  must include either &#x60;email&#x60; or &#x60;sms_number&#x60; as a column heading. Other properties you can include using column headings are: &#x60;first_name&#x60;.  &#x60;last_name&#x60;, &#x60;phone&#x60;, &#x60;job_title&#x60;, &#x60;anniversary&#x60;, &#x60;birthday_day&#x60;, &#x60;birthday_month&#x60;, &#x60;company_name&#x60;, &#x60;street&#x60;, &#x60;street2&#x60;, &#x60;city&#x60;, &#x60;state&#x60;, &#x60;zip&#x60;, &#x60;country&#x60;, and &#x60;sms_consent_date&#x60;.   If adding an &#x60;sms_number&#x60;, you must also include the &#x60;sms_permission_to_send&#x60; parameter and set it to either &#x60;not_set&#x60; or &#x60;explicit&#x60;. If &#x60;explicit&#x60;, requires including &#x60;sms_consent_date&#x60; as a column header to specify the date the contact consented to receiving SMS messages.   You can also use custom fields as column headings. Enter the custom field name prefixed with &#x60;cf:&#x60; as the column heading. For example, use &#x60;cf:first_name&#x60; as the header name if you have a custom field named \\\&quot;first_name\\\&quot;. The custom field must already exist in the Constant Contact account you are using. Depending on the custom field data type, you can enter dates or strings as the value of the custom field. Each contact can contain up to 25 different custom fields. |  |
+| **list_ids** | **String** | Specify which contact lists you are adding all imported contacts to as an array of up to 50 contact &#x60;list_id&#x60; values. |  |
+| **sms_permission_to_send** | **String** | If importing contact &#x60;sms_number&#x60;s, use this parameter to specify how SMS consent was provided. If all contacts in the file provided their consent, set to &#x60;explicit&#x60; and include each contact&#39;s &#x60;sms_consent_date&#x60;. If all contacts in the file have not yet provided consent, set to &#x60;not_set&#x60; (&#x60;sms_consent_date&#x60; is not required). You cannot message a contact that does not have a sms consent date set. | [optional] |
 
 ### Return type
 
@@ -172,7 +176,7 @@ end
 
 Export Contacts to a File
 
-Use this method to create an activity that exports contacts and contact details to a CSV file. By default, all contacts are exported. To filter contacts to export, specify the source to use, `contact_id`, `list_id`, or `segment_id` (all mutually exclusive). By default, all contact related fields are exported. Use the fields array to only export specific contact fields. You must export `email_address` to successfully export `email_optin_source`, `email_optin_date`, `email_optout_source`, `email_optout_date`, or `email_optout_reason`. After Constant Contact finishes processing the activity, use the `results` link in the response body to retrieve the CSV file.
+Use this method to create an activity that exports contacts and contact details to a CSV file.  You can choose to export all contacts in your account (default) or you can use parameters to filter on which contacts to export. After Constant Contact finishes processing the activity, use the `results` link in the response body to retrieve the CSV file.
 
 ### Examples
 
@@ -244,7 +248,7 @@ end
 
 Import Contacts using a JSON Payload
 
-Use this method to create an asynchronous background job that adds new contacts or updates existing contacts by importing a JSON payload. This method requires a request body that contains the contact data you are importing and the contact lists to which you want to add the imported contacts. Importing a new contact automatically sets the contact's `permission_to_send` property as `implicit` and the `opt_in_source` property as `Account`. Importing an existing contact only updates the contact properties you include in the request. For each contact, you can import up to three addresses and three phone numbers. International phone numbers are currently not supported. To import custom fields, prefix the custom field name with `cf:` and add it as a contact property. For example, use the property name `cf:first_name` if you have a custom field named first_name. The custom field must already exist in the Constant Contact account you are using. Each contact can contain up to 25 custom fields.  The request body payload has a maximum size of 4 megabytes (MB). If the request body exceeds 4 MB, this method only imports the first 4 MB and drops the remaining data. Use the activity URL to check the status of the import activity request.
+Use this method to create an asynchronous background job that adds new contacts or updates existing contacts by importing a JSON payload. This method requires a request body that contains the contact data you are importing and the contact lists to which you want to add the imported contacts. A contact's data must include an `email` address and/or `sms_number`. The `sms_number` must be a US phone number to associate with the contact's SMS-enabled phone. Valid formats are <code>1231231234</code> or <code>123-123-1234</code> (the country code must be valid).  Importing a new contact using this method automatically sets the contact's email `permission_to_send` property to `implicit` and the `opt_in_source` property as `Account`. Importing an existing contact only updates the contact properties you include in the request. For each contact, you can import up to three addresses and three phone numbers. International phone numbers are currently not supported.        To import custom fields, prefix the custom field name with `cf:` and add it as a contact property. For example, use the property name `cf:first_name` if you have a custom field named `first_name`. The custom field must already exist in the Constant Contact account you are using. Each contact can contain up to 25 custom fields.  To include a contact's `sms_number`, if the contact provided explicit permission to receive SMS messages, you must set the `sms_permission_to_send` property to `explicit` and specify the date of consent using the `sms_consent_date` column header. If explicit permission was not provided, set `sms_permission_to_send` to `not_set` (the `sms_consent_date` is not required). If the `sms_consent_date` is not set, SMS messages cannot be sent to contacts and `sms_permission_to_send` defaults to `not_set`. Valid value formats for `sms_consent_date` include MM/DD/YYYY, M/D/YYYY, YYYY/MM/DD, YYYY/M/D, YYYY-MM-DD, YYYY-M-D,M-D-YYYY, or M-DD-YYYY.   The request body payload has a maximum size of 4 megabytes (MB). If the request body exceeds 4 MB, this method only imports the first 4 MB and drops the remaining data. Use the activity URL to check the status of the import activity request.
 
 ### Examples
 
@@ -261,7 +265,7 @@ ConstantContactClient.configure do |config|
 end
 
 api_instance = ConstantContactClient::BulkActivitiesApi.new
-create_import_json_activity_request = ConstantContactClient::CreateImportJSONActivityRequest.new({import_data: [ConstantContactClient::CreateImportJSONActivityRequestImportDataInner.new({email: 'joe.jones@example.com'})], list_ids: ['04fe9a97-a579-43c5-bb1a-58ed29bf0a6a']}) # CreateImportJSONActivityRequest | The JSON request payload that contains the contact data and contact lists for the import.
+create_import_json_activity_request = ConstantContactClient::CreateImportJSONActivityRequest.new({import_data: [ConstantContactClient::CreateImportJSONActivityRequestImportDataInner.new], list_ids: ['04fe9a97-a579-43c5-bb1a-58ed29bf0a6a']}) # CreateImportJSONActivityRequest | The JSON request payload that contains the contact data and contact lists for the import.
 
 begin
   # Import Contacts using a JSON Payload

data/docs/ContactListsApi.md

@@ -184,7 +184,9 @@ opts = {
   include_count: true, # Boolean | Set `include_count` to `true` to return the total number of contact lists that meet your selection criteria.
   include_membership_count: 'all', # String | Use to include the total number of contacts per list. Set to  `active`, to count only active (mailable) contacts, or `all` to count all contacts.
   name: 'TopTier', # String | Use to get details for a single list by entering the full name of the list.
-  status: 'all' # String | Use to get lists by status. Accepts comma-separated status values.
+  status: 'all', # String | Use to get lists by status. Accepts comma-separated status values.
+  channel_type: 'email', # String | Use to return lists by channel type. The default value is `email`.
+  include_sms_membership_count: false # Boolean | Set to `true` to return the total number of SMS members in each list. Only applicable when `channel_type` is `sms`. Default is `false`.
 }
 
 begin
@@ -223,6 +225,8 @@ end
 | **include_membership_count** | **String** | Use to include the total number of contacts per list. Set to  `active`, to count only active (mailable) contacts, or `all` to count all contacts. | [optional] |
 | **name** | **String** | Use to get details for a single list by entering the full name of the list. | [optional] |
 | **status** | **String** | Use to get lists by status. Accepts comma-separated status values. | [optional] |
+| **channel_type** | **String** | Use to return lists by channel type. The default value is `email`. | [optional] |
+| **include_sms_membership_count** | **Boolean** | Set to `true` to return the total number of SMS members in each list. Only applicable when `channel_type` is `sms`. Default is `false`. | [optional] |
 
 ### Return type
 

data/docs/ContactsApi.md

@@ -12,6 +12,7 @@ All URIs are relative to *https://api.cc.email/v3*
 | [**get_contact_counts**](ContactsApi.md#get_contact_counts) | **GET** /contacts/counts | GET Contact Consent Counts |
 | [**get_contact_id_xrefs**](ContactsApi.md#get_contact_id_xrefs) | **GET** /contacts/contact_id_xrefs | GET a collection of V2 and V3 API contact IDs |
 | [**get_sms_engagement_history**](ContactsApi.md#get_sms_engagement_history) | **GET** /contacts/sms_engagement_history/{contact_id} | GET SMS Engagement History for a Contact |
+| [**resubscribe_contact**](ContactsApi.md#resubscribe_contact) | **PUT** /contacts/resubscribe/{contact_id} | PUT Resubscribe a Contact |
 | [**update_contact**](ContactsApi.md#update_contact) | **PUT** /contacts/{contact_id} | PUT (update) a Contact |
 
 
@@ -21,7 +22,7 @@ All URIs are relative to *https://api.cc.email/v3*
 
 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>
 
 ### Examples
 
@@ -93,7 +94,7 @@ 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.       
+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.       
 
 ### Examples
 
@@ -110,7 +111,7 @@ ConstantContactClient.configure do |config|
 end
 
 api_instance = ConstantContactClient::ContactsApi.new
-create_or_update_contact_request = ConstantContactClient::CreateOrUpdateContactRequest.new({email_address: 'jdodge@example.com', list_memberships: ['07936f78-662a-11eb-af0a-fa163e56c9b0']}) # CreateOrUpdateContactRequest | A JSON request body payload that contains the contact resource you are creating or updating. The request body must contain the `email_address` property and the `list_memberships` array.
+create_or_update_contact_request = ConstantContactClient::CreateOrUpdateContactRequest.new({list_memberships: ['07936f78-662a-11eb-af0a-fa163e56c9b0']}) # CreateOrUpdateContactRequest | A JSON request body payload that contains the contact resource you are creating or updating. The request body must contain the `email_address` property and `list_memberships` array, or the `sms_channel` object.
 
 begin
   # Create or Update a Contact
@@ -143,7 +144,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **create_or_update_contact_request** | [**CreateOrUpdateContactRequest**](CreateOrUpdateContactRequest.md) | 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. |  |
+| **create_or_update_contact_request** | [**CreateOrUpdateContactRequest**](CreateOrUpdateContactRequest.md) | 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. |  |
 
 ### Return type
 
@@ -236,7 +237,7 @@ nil (empty response body)
 
 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.
 
 ### Examples
 
@@ -265,7 +266,7 @@ opts = {
   created_before: Time.parse('2022-07-16T16:37:59.091Z'), # Time | Use `created_before` to search for contacts created before a specified date. To search for contacts created within a date range, specify both `created_after` and `created_before` dates. Accepts ISO-8601 formatted dates.
   optout_after: Time.parse('2022-11-16T16:20:59.091Z'), # Time | Use `optout_after` to search for contacts that unsubscribed after a specified date.
   optout_before: Time.parse('2022-11-16T16:20:59.091Z'), # Time | Use `optout_before` to search for contacts that unsubscribed before a specified date.
-  include: 'custom_fields', # String | Use `include` to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: `custom_fields`, `list_memberships`, `taggings`, `notes`,`phone_numbers`, `street_addresses`, `sms_channel`.
+  include: 'custom_fields', # String | Use `include` to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: `custom_fields`, `list_memberships`, `taggings`, `notes`,`phone_numbers`, `street_addresses`.
   sms_status: 'all', # String | Use to get contacts by their SMS status. This parameter accepts one or more comma separated values: `all`, `explicit`, `unsubscribed`, `pending_confirmation`, `not_set`.
   include_count: true, # Boolean | Set `include_count=true` to include the total number of contacts (`contacts_count`) that meet all search criteria in the response body.
   limit: 25 # Integer | Specifies the number of results displayed per page of output in the response, from 1 - 500, default = 50.
@@ -313,7 +314,7 @@ end
 | **created_before** | **Time** | 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. | [optional] |
 | **optout_after** | **Time** | Use &#x60;optout_after&#x60; to search for contacts that unsubscribed after a specified date. | [optional] |
 | **optout_before** | **Time** | Use &#x60;optout_before&#x60; to search for contacts that unsubscribed before a specified date. | [optional] |
-| **include** | **String** | 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;. | [optional] |
+| **include** | **String** | 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;. | [optional] |
 | **sms_status** | **String** | 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;. | [optional] |
 | **include_count** | **Boolean** | 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. | [optional] |
 | **limit** | **Integer** | Specifies the number of results displayed per page of output in the response, from 1 - 500, default &#x3D; 50. | [optional][default to 50] |
@@ -357,7 +358,7 @@ end
 api_instance = ConstantContactClient::ContactsApi.new
 contact_id = '04fe9a-a579-43c5-bb1a-58ed29bf0a6a' # String | Unique ID of contact to GET
 opts = {
-  include: 'custom_fields' # String | Use `include` to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: `custom_fields`, `list_memberships`, `phone_numbers`, `street_addresses`, `notes`, `sms_channel`, and `taggings`.
+  include: 'custom_fields' # String | Use `include` to specify which contact sub-resources to include in the response. Use a comma to separate multiple sub-resources. Valid values: `custom_fields`, `list_memberships`, `phone_numbers`, `street_addresses`, `notes`, and `taggings`.
 }
 
 begin
@@ -392,7 +393,7 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **contact_id** | **String** | Unique ID of contact to GET |  |
-| **include** | **String** | 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;. | [optional] |
+| **include** | **String** | 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;. | [optional] |
 
 ### Return type
 
@@ -626,13 +627,86 @@ end
 - **Accept**: application/json
 
 
+## resubscribe_contact
+
+> resubscribe_contact(contact_id, resubscribe_contact_request)
+
+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. 
+
+### Examples
+
+```ruby
+require 'time'
+require 'constant_contact_client'
+# setup authorization
+ConstantContactClient.configure do |config|
+  # Configure OAuth2 access token for authorization: oauth2_access_code
+  config.access_token = 'YOUR ACCESS TOKEN'
+
+  # Configure OAuth2 access token for authorization: oauth2_implicit
+  config.access_token = 'YOUR ACCESS TOKEN'
+end
+
+api_instance = ConstantContactClient::ContactsApi.new
+contact_id = '04fe9a-a579-43c5-bb1a-58ed29bf0a6a' # String | The ID that uniquely identifies the contact to resubscribe.
+resubscribe_contact_request = ConstantContactClient::ResubscribeContactRequest.new({list_ids: ['04fe9a97-a579-43c5-bb1a-58ed29bf0a6a']}) # ResubscribeContactRequest | The JSON payload used to specify one (or more) contact lists to which the contact requested to be resubscribed.
+
+begin
+  # PUT Resubscribe a Contact
+  api_instance.resubscribe_contact(contact_id, resubscribe_contact_request)
+rescue ConstantContactClient::ApiError => e
+  puts "Error when calling ContactsApi->resubscribe_contact: #{e}"
+end
+```
+
+#### Using the resubscribe_contact_with_http_info variant
+
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
+
+> <Array(nil, Integer, Hash)> resubscribe_contact_with_http_info(contact_id, resubscribe_contact_request)
+
+```ruby
+begin
+  # PUT Resubscribe a Contact
+  data, status_code, headers = api_instance.resubscribe_contact_with_http_info(contact_id, resubscribe_contact_request)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue ConstantContactClient::ApiError => e
+  puts "Error when calling ContactsApi->resubscribe_contact_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **contact_id** | **String** | The ID that uniquely identifies the contact to resubscribe. |  |
+| **resubscribe_contact_request** | [**ResubscribeContactRequest**](ResubscribeContactRequest.md) | The JSON payload used to specify one (or more) contact lists to which the contact requested to be resubscribed. |  |
+
+### Return type
+
+nil (empty response body)
+
+### Authorization
+
+[oauth2_access_code](../README.md#oauth2_access_code), [oauth2_implicit](../README.md#oauth2_implicit)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: Not defined
+
+
 ## update_contact
 
 > <GetContactById200Response> update_contact(contact_id, update_contact_request)
 
 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>
 
 ### Examples