---
title: "POST (Create) a New Email Campaign"
method: POST
path: "/emails"
tags: ["Email Campaigns"]
---

# POST (Create) a New Email Campaign

`POST /emails`

Use this method to create a new email campaign. The API supports custom HTML campaigns (format type 5). Custom HTML must include a tracking image (`[[trackingImage]]`) in the email body in order for Constant Contact to report on the email performance.
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.

## Request body

- EmailCampaignComplete
  - `name` string, required — The unique and descriptive name that you specify for the email campaign.
  - `email_campaign_activities` EmailCampaignActivityInput[], required — The content of the email campaign as an array that contains a single email campaign activity object.
    - `format_type` integer, required — The email format you are using to create the email campaign activity. The V3 API supports creating emails using <code>format_type</code> 4 (email editor) and 5 (custom code emails).
    - `from_name` string, required — The email sender's name to display for the email campaign activity.
    - `from_email` string, required — The sender's email address to use for the email campaign activity. You must use a confirmed Constant Contact account email address. Make a GET call to <code>/account/emails</code> to return a collection of account emails and their confirmation status.
    - `reply_to_email` string, required — The sender's email address to use if the contact replies to the email campaign activity. You must use a confirmed Constant Contact account email address. Make a GET call to <code>/account/emails</code> to return a collection of account emails and their confirmation status.
    - `subject` string, required — The text to display in the subject line that describes the email campaign activity.
    - `preheader` string — The email preheader for the email campaign activity. Contacts will view your preheader as a short summary that follows the subject line in their email client. Only <code>format_type</code> 3, 4, and 5 email campaign activities use the preheader property.
    - `html_content` string, required — The HTML content for the email campaign activity. Only <code>format_type</code> 5 (custom code emails) can contain <code>html_content</code>. When creating a <code>format_type</code> 5 custom code email, make sure that you include <code>[[trackingImage]]</code> in the <code>&lt;body&gt;</code> element of your HTML.
    - `physical_address_in_footer` EmailPhysicalAddress
      - `address_line1` string, required — Line 1 of the organization's street address.
      - `address_line2` string — Line 2 of the organization's street address.
      - `address_line3` string — Line 3 of the organization's street address.
      - `address_optional` string — An optional address field for the organization. Only <code>format_type</code> 3, 4, and 5 can use this property.
      - `city` string — The city where the organization sending the email campaign is located.
      - `country_code` string, required — The uppercase two letter <a href='https://en.wikipedia.org/wiki/ISO_3166-1' target='_blank'>ISO 3166-1 code</a> for the organization's country.
      - `country_name` string — The full name of the country where the organization sending the email is located. Automatically generated using the <code>country_code</code>.
      - `organization_name` string, required — The name of the organization that is sending the email campaign.
      - `postal_code` string — The postal code address (ZIP code) of the organization.
      - `state_code` string — The uppercase two letter <a href='https://en.wikipedia.org/wiki/ISO_3166-1' target='_blank'>ISO 3166-1 code</a> for the organization's state. This property is required if the <code>country_code</code> is US (United States).
      - `state_name` string — The full state name for a <code>state_code</code> that is inside the United States. Automatically generated using the <code>state_code</code>.
      - `state_non_us_name` string — The full state name for a <code>state_code</code> that is outside the United States. This property is not read only.

## Response `200`

Request successful. NOTE: If you created an email campaign using a legacy (V7) format, Constant Contact successfully converted it to the newer custom code format.

- EmailCampaign
  - `campaign_activities` ActivityReference[] — Lists the role and unique activity ID of each campaign activity that is associated with an Email Campaign.
    - `campaign_activity_id` string — The ID (UUID) that uniquely identifies a campaign activity.
    - `role` string — The purpose of the individual campaign activity in the larger email campaign effort. Valid values are: <ul> <li>primary_email — The main email marketing campaign that you send to contacts. The <code>primary_email</code> contains the complete email content.</li> <li>permalink — A permanent link to a web accessible version of the <code>primary_email</code> content without any personalized email information. For example, permalinks do not contain any of the contact details that you add to the <code>primary_email</code> email content. </li> <li>resend — An email campaign that you resend to contacts that did not open the email campaign.</li> </ul> Constant Contact creates a <code>primary_email</code> and a <code>permalink</code> role campaign activity when you create an email campaign.
    - `document_id` string — Identifies the email document used in an email editor (format_type 4) email campaign.
  - `campaign_id` string — The unique ID used to identify the email campaign (UUID format).
  - `created_at` string, date-time — The system generated date and time that this email campaign was created. This string is readonly and is in ISO-8601 format.
  - `current_status` string — The current status of the email campaign. Valid values are: <ul> <li>Draft — An email campaign that you have created but have not sent to contacts.</li> <li>Scheduled — An email campaign that you have scheduled for Constant Contact to send to contacts.</li> <li>Executing — An email campaign that Constant Contact is currently sending to contacts. Email campaign activities are only in this status briefly.</li> <li>Done — An email campaign that you successfully sent to contacts.</li> <li>Error — An email campaign activity that encountered an error.</li> <li>Removed — An email campaign that a user deleted. Users can view and restore deleted emails through the UI.</li> </ul>
  - `name` string — The descriptive name the user provides to identify this campaign. Campaign names must be unique for each account ID.
  - `type` string — Identifies the type of campaign that you select when creating the campaign. Newsletter and Custom Code email campaigns are the primary types.
  - `type_code` integer — The code used to identify the email campaign `type`. <ul> <li> 1 (Default) </li> <li> 2 (Bulk Email) </li> <li> 10 (Newsletter) </li> <li> 11 (Announcement) </li> <li> 12 (Product/Service News) </li> <li> 14 (Business Letter) </li> <li> 15 (Card) </li> <li> 16 (Press release)</li> <li> 17 (Flyer) </li> <li> 18 (Feedback Request) </li> <li> 19 (Ratings and Reviews) </li> <li> 20 (Event Announcement) </li> <li> 21 (Simple Coupon) </li> <li> 22 (Sale Promotion) </li> <li> 23 (Product Promotion) </li> <li> 24 (Membership Drive) </li> <li> 25 (Fundraiser) </li> <li> 26 (Custom Code Email)</li> <li> 57 (A/B Test)</li> </ul>
  - `updated_at` string, date-time — The system generated date and time showing when the campaign was last updated. This string is read only and is in ISO-8601 format.

## 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.
- `429` — Too many requests. You exceeded the request rate limit.
- `500` — There was a problem with our internal service.

---

[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)