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.
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.
Contact or Account. Your integration must accurately identify create_source for compliance reasons; value is set on POST, and is read-only going forward.
- `birthday_month` integer — The month value for the contact's birthday. Valid values are from 1 through 12. The birthday_month property is required if you use birthday_day.
- `birthday_day` integer — The day value for the contact's birthday. Valid values are from 1 through 31. The birthday_day property is required if you use birthday_month.
- `anniversary` string — The anniversary date for the contact. For example, this value could be the date when the contact first became a customer of an organization in Constant Contact. Valid date formats are 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.
- `custom_fields` ContactCustomField[] — Array of up to 25 custom_field key value pairs.
- `custom_field_id` string, uuid, required — The custom field's unique ID
- `value` string — The custom field value.
- `choice_ids` string[] — For >multi_select and single_select data types, the ID that uniquely identifies the choice associated with a the custom field.
- `phone_numbers` PhoneNumberPut[] — Array of up to 3 phone numbers subresources.
- `phone_number` string — The contact's phone number.
- `kind` string — Identifies the type of phone number; valid values are home, work, mobile, or other.
- `street_addresses` StreetAddressPut[] — Array of up to 3 street address subresources.
- `kind` string, required — Describes the type of address; valid values are home, work, or other.
- `street` string — Number and street of the address.
- `city` string — The name of the city where the contact lives.
- `state` string — The name of the state or province where the contact lives.
- `postal_code` string — The zip or postal code of the contact.
- `country` string — The name of the country where the contact lives.
- `list_memberships` string[] — Array of list_ids to which the contact is being subscribed, up to a maximum of 50.
- `taggings` string[] — Array of tags (tag_id) assigned to the contact, up to a maximum of 50.
- `notes` Note[] — An array of notes about the contact.
- `note_id` string, uuid — The ID that uniquely identifies the note (UUID format).
- `created_at` string, date-time — The date that the note was created.
- `content` string — The content for the note.
- `sms_channel` ContactSmsChannel
- `full_sms_address` string, required — The SMS-capable phone number for the Contact, including the dial code
- `sms_channel_consents` ContactSmsChannelConsents[], required — The consents for the SMS Channel.
- `sms_consent_permission` string, required — The current status of the SMS channel.
- `consent_type` string, required — The type of consent provided.
- `consent_medium_details` string — Additional information about the consent such as the type of device used.
## Response `201`
New contact successfully created
- ContactResource — Use this endpoint to retrieve (GET), update (PUT), or DELETE an existing contact resource specified using the contact_id path parameter.
- `contact_id` string, uuid — Unique ID for each contact resource
- `email_address` EmailAddress — A contact subresource describing the contact's email address.
- `address` string, required — The email address of the contact. The email address must be unique for each contact.
- `permission_to_send` string — Identifies the type of permission that the Constant Contact account has to send email to the contact. Types of permission: explicit, implicit, not_set, pending_confirmation, temp_hold, unsubscribed.
- `created_at` string, date-time — Date and time that the email_address was created, in ISO-8601 format. System generated.
- `updated_at` string, date-time — Date and time that the email_address was last updated, in ISO-8601 format. System generated.
- `opt_in_source` string — Describes who opted-in the email_address; valid values are Contact or Account. Your integration must accurately identify opt_in_source for compliance reasons; value is set on POST, and is read-only going forward.
- `opt_in_date` string, date-time — Date and time that the email_address was opted-in to receive email from the account, in ISO-8601 format. System generated.
- `opt_out_source` string — Describes the source of the unsubscribed/opt-out action: either Account or Contact. If the Contact opted-out, then the account cannot send any campaigns to this contact until the contact opts back in. If the Account, then the account can add the contact back to any lists and send to them. Displayed only if contact has been unsubscribed/opt-out.
- `opt_out_date` string, date-time — Date and time that the contact unsubscribed/opted-out of receiving email from the account, in ISO-8601 format. Displayed only if contact has been unsubscribed/opt-out. System generated.
- `opt_out_reason` string — The reason, as provided by the contact, that they unsubscribed/opted-out of receiving email campaigns.
- `confirm_status` string — Indicates if the contact confirmed their email address after they subscribed to receive emails. Possible values: pending, confirmed, off.
- `first_name` string — The first name of the contact.
- `last_name` string — The last name of the contact.
- `job_title` string — The job title of the contact.
- `company_name` string — The name of the company where the contact works.
- `birthday_month` integer — The month value for the contact's birthday. Valid values are from 1 through 12. You must use this property with birthday_month.
- `birthday_day` integer — The day value for the contact's birthday. Valid values are from 1 through 12. You must use this property with birthday_day.
- `anniversary` string — The anniversary date for the contact. For example, this value could be the date when the contact first became a customer of an organization in Constant Contact. Valid date formats are 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.
- `update_source` string — Identifies who last updated the contact; valid values are Contact or Account.
- `create_source` string — Describes who added the contact; valid values are Contact or Account. Your integration must accurately identify create_source for compliance reasons; value is set when contact is created.
- `created_at` string, date-time — System generated date and time that the resource was created, in ISO-8601 format.
- `updated_at` string, date-time — System generated date and time that the contact was last updated, in ISO-8601 format.
- `deleted_at` string, date — For deleted contacts (email_address contains opt_out_source and opt_out_date), shows the date of deletion.
- `custom_fields` ContactCustomField[] — Array of up to 25 custom_field subresources.
- `custom_field_id` string, uuid, required — The custom field's unique ID
- `value` string — The custom field value.
- `choice_ids` string[] — For >multi_select and single_select data types, the ID that uniquely identifies the choice associated with a the custom field.
- `phone_numbers` PhoneNumber[] — Array of up to 3 phone_numbers subresources.
- `phone_number_id` string, uuid — Unique ID for the phone number
- `phone_number` string — The contact's phone number.
- `kind` string — Identifies the type of phone number; valid values are home, work, mobile, or other.
- `created_at` string, date-time — Date and time that the street address was created, in ISO-8601 format. System generated.
- `updated_at` string, date-time — Date and time that the phone number was last updated, in ISO-8601 format. System generated.
- `update_source` string — Identifies who last updated the phone number; valid values are Contact or Account
- `create_source` string — Identifies who added the phone number; valid values are Contact or Account.
- `street_addresses` StreetAddress[] — Array of up to 3 street_addresses subresources.
- `street_address_id` string, uuid — Unique ID for the street address
- `kind` string, required — Describes the type of address; valid values are home, work, or other.
- `street` string — Number and street of the address.
- `city` string — The name of the city where the contact lives.
- `state` string — The name of the state or province where the contact lives.
- `postal_code` string — The zip or postal code of the contact.
- `country` string — The name of the country where the contact lives.
- `created_at` string, date-time — Date and time that the street address was created, in ISO-8601 format. System generated.
- `updated_at` string, date-time — Date and time that the street address was last updated, in ISO-8601 format. System generated.
- `list_memberships` string[] — Array of up to 50 list_ids to which the contact is subscribed.
- `taggings` string[] — Array of tags (tag_id) assigned to the contact, up to a maximum of 50.
- `notes` Note[] — An array of notes about the contact listed by most recent note first.
- `note_id` string, uuid — The ID that uniquely identifies the note (UUID format).
- `created_at` string, date-time — The date that the note was created.
- `content` string — The content for the note.
- `sms_channel` object — Includes SMS channel and consent details.
- `sms_channel_id` string, uuid — The unique ID that identifies an SMS channel.
- `sms_address` string — The phone number of the SMS-capable phone, which does not include the country code.
- `dial_code` string — The dial code used for the SMS-capable phone. For example, the dial code for the United States is 1.
- `country_code` string — The two character ISO country code used for the SMS-capable phone. For example, the country code for the United States is US.
- `update_source` string — Identifies who last updated SMS details for the contact. Valid values are Contact or Account
- `create_source` string — Identifies who added SMS details for the contact. The value is set when you create SMS details for the contact. Valid values are Contact or Account.
- `sms_channel_consents` SmsChannelConsentDetails[] — Identifies SMS channel consent details such as the current permission status for the SMS channel and opt-in date.
- `sms_consent_permission` string — Identifies the current permission status for the SMS channel.
- `consent_type` string — Identifies the type of consent provided. Currently, only promotional_sms is supported.
- `opt_in_date` string, date-time — Date and time, in ISO-8601 format, that the contact subscribed/opted-in to receiving SMS from the account. Displays only if the contact subscribes/opts-in. System generated.
- `opt_out_date` string, date-time — Date and time, in ISO-8601 format, that the contact unsubscribed/opted-out of receiving SMS from the account. Displays only if the contact unsubscribed/opted-out. System generated.
- `advertised_frequency` string — The numeric used to set how often to send SMS advertisements during a specified time interval (advertised_interval). For example, if the advertised_frequency is set to 2 and the advertised_interval is set to monthly, the contact can receive up to two advertisements per month.
- `advertised_interval` string — Identifies the unit of time used by Constant Contact to send SMS advertisements as a string enum. For example, if the advertised_frequency is set to 2 and the advertised_interval is set to monthly, the contact can receive up to two advertisements per month.
- `created_at` string, date-time — Date and time that the SMS stats were created, in ISO-8601 format. System generated.
- `updated_at` string, date-time — Date and time that the SMS stats were updated, in ISO-8601 format. System generated.
## Other responses
- `400` — Bad request. Either the JSON was malformed or there was a data validation error.
- `401` — The Access Token used is invalid.
- `403` — Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
- `409` — Conflict. The resource you are creating or updating conflicts with an existing resource.
- `415` — Unsupported Media Type; the payload must be in JSON format, and Content-Type must be application/json
- `500` — There was a problem with our internal service.
- `503` — Our internal service is temporarily unavailable.
---
[API](https://skmtc.net/cc/apis/appconnect-v3.md) · [All operations](https://skmtc.net/cc/apis/appconnect-v3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cc/appconnect-v3/revisions/4b4a534c818d/schema)