V25.5.0 - 2025-05-10

Author: phpfui

src/ConstantContact/Definition/ContactCreateOrUpdateInput.php

@@ -17,7 +17,7 @@
  * @property int $birthday_month The month value for the contact's birthday. Valid values are from 1 through 12. The <code>birthday_month</code> property is required if you use <code>birthday_day</code>.
  * @property int $birthday_day The day value for the contact's birthday. Valid values are from 1 through 31. The <code>birthday_day</code> property is required if you use <code>birthday_month</code>.
  * @property \PHPFUI\ConstantContact\Definition\StreetAddress $street_address
- * @property string $sms_channel The contact's SMS compatible phone number.
+ * @property \PHPFUI\ConstantContact\Definition\JmmlSmsChannel $sms_channel
  */
 class ContactCreateOrUpdateInput extends \PHPFUI\ConstantContact\Definition\Base
 	{
@@ -34,7 +34,7 @@ class ContactCreateOrUpdateInput extends \PHPFUI\ConstantContact\Definition\Base
 		'birthday_month' => 'int',
 		'birthday_day' => 'int',
 		'street_address' => '\PHPFUI\ConstantContact\Definition\StreetAddress',
-		'sms_channel' => 'string',
+		'sms_channel' => '\PHPFUI\ConstantContact\Definition\JmmlSmsChannel',
 
 	];
 

src/ConstantContact/V3/Activities/ContactsFileImport.php

@@ -42,10 +42,10 @@ public function __construct(\PHPFUI\ConstantContact\Client $client)
 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.
-	 * @param array $list_ids Specify which contact lists you are adding all imported contacts to as an array of up to 50 contact `list_id` values.
+	 * @param string $list_ids Specify which contact lists you are adding all imported contacts to as an array of up to 50 contact `list_id` values.
 	 * @param string $sms_permission_to_send 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.
 	 */
-	public function post(string $file, array $list_ids, ?string $sms_permission_to_send = null) : ?array
+	public function post(string $file, string $list_ids, ?string $sms_permission_to_send = null) : ?array
 		{
 
 		if (null !== $sms_permission_to_send)
@@ -61,7 +61,7 @@ public function post(string $file, array $list_ids, ?string $sms_permission_to_s
 		return $this->doPost(['file' => $file, 'list_ids' => $list_ids, 'sms_permission_to_send' => $sms_permission_to_send, ]);
 		}
 
-	public function postTyped(string $file, array $list_ids, ?string $sms_permission_to_send = null) : ?\PHPFUI\ConstantContact\Definition\ActivityImport
+	public function postTyped(string $file, string $list_ids, ?string $sms_permission_to_send = null) : ?\PHPFUI\ConstantContact\Definition\ActivityImport
 		{
 		$data = $this->post($file, $list_ids, $sms_permission_to_send);
 

src/ConstantContact/V3/Contacts/SignUpForm.php

@@ -28,6 +28,7 @@ public function __construct(\PHPFUI\ConstantContact\Client $client)
 	 * 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
@@ -41,6 +42,7 @@ public function __construct(\PHPFUI\ConstantContact\Client $client)
 	 * 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.

yaml/swagger.yaml

@@ -3,7 +3,7 @@ swagger: "2.0"
 info:
   description: "The Constant Contact, Inc. V3 public API, for building integrations\
     \ with Constant Contact, the leading small-business email marketing platform."
-  version: "3.0.53"
+  version: "3.0.62"
   title: "AppConnect V3"
   contact:
     name: "[email protected]"
@@ -59,6 +59,8 @@ tags:
 - name: "Technology Partners Webhooks"
   description: "Use partner webhooks to subscribe to billing event notifications from\
     \ Constant Contact."
+- name: "Integrations"
+  description: "Endpoints and methods used for integrations."
 schemes:
 - "https"
 consumes:
@@ -802,10 +804,11 @@ paths:
         description: "Specify which contact lists you are adding all imported contacts\
           \ to as an array of up to 50 contact `list_id` values."
         required: true
-        type: "array"
+        type: "string"
         items:
           type: "string"
         maxItems: 50
+        format: "csv"
         x-example: "8c077f20-1586-11e4-bcb3-00163e56be7c"
       - name: "sms_permission_to_send"
         in: "formData"
@@ -2090,7 +2093,7 @@ paths:
         \nUpdates 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.\nIf `email_address` is specified: <div class=\"Msg\"><p class=\"\
+        \ arrays.\n\nIf `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\
@@ -2101,7 +2104,7 @@ paths:
         \ 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>\n\
-        When this method creates a new contact, it returns a 201 response code.When\
+        \nWhen 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.\n\nThe method automatically\
         \ modifies the contact's `permission_to_send` and `opt_in_source` properties\
@@ -9276,6 +9279,7 @@ definitions:
         description: "The consents provided for the SMS Channel."
         items:
           $ref: "#/definitions/JmmlSmsChannelConsents"
+    description: "The contact's SMS details."
   ContactCreateOrUpdateInput:
     type: "object"
     required:
@@ -9387,8 +9391,7 @@ definitions:
         required:
         - "kind"
       sms_channel:
-        type: "string"
-        description: "The contact's SMS compatible phone number."
+        $ref: "#/definitions/JmmlSmsChannel"
   ContactCreateOrUpdateResponse:
     type: "object"
     properties: