Constant Contact Email Campaigns API

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.149
  title: AppConnect V3 Account Services Email Campaigns API
  contact:
    name: webservices@constantcontact.com
  license:
    name: Private
    url: https://www.constantcontact.com/legal/terms-of-use
host: api.cc.email
basePath: /v3
schemes:
- https
consumes:
- application/json
produces:
- application/json
tags:
- name: Email Campaigns
  description: Use email campaign endpoints and methods to get, create, and update email campaigns.
paths:
  /emails:
    get:
      tags:
      - Email Campaigns
      summary: GET a Collection of Email Campaigns
      description: 'Use this method to list and get details about your email campaigns. By default, this method returns all email campaigns for the user account including deleted email campaigns. To get email campaigns within a date-range, use the `after_date` and `before_date` query parameters.


        This endpoint does not return campaign activity details for each email campaign in the collection. To get email campaign activity details for a single email campaign, use the GET `/emails/{campaign_id}` endpoint."

        <div class="Msg"><p class="note-text">This method does not currently support filtering results using the email campaign creation date.</p></div>

        '
      operationId: retrieveEmailCampaignsUsingGET
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: limit
        in: query
        description: Specifies the number of campaigns to display on each page of output that is returned (from return 1 - 500). The default returns 50 campaigns per page.
        required: false
        type: integer
        default: 50
        format: int32
      - name: before_date
        in: query
        description: Use to return email campaigns with `updated_at` timestamps that are before a specific date and time (in ISO-8601 format). Use with the `after_date` query parameter to get email campaigns sent within a specific date range.
        required: false
        type: string
        format: date-time
        x-example: '2021-01-10T11:42:57.000Z'
      - name: after_date
        in: query
        description: Use to return email campaigns with last `updated_at` timestamps that are after a specific date and time (in ISO-8601 format). Use with the `before_date` query parameter to get email campaigns sent within a specific date range.
        required: false
        type: string
        format: date-time
        x-example: '2021-03-10T11:42:57.000Z'
      responses:
        '200':
          description: Request successful.
          schema:
            $ref: '#/definitions/PagedEmailCampaignResponse'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:read
      x-sdk-methodName: getAllEmailCampaigns
    post:
      tags:
      - Email Campaigns
      summary: POST (Create) a New Email Campaign
      description: '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.

        '
      operationId: createEmailCampaignUsingPOST
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - in: body
        name: body
        description: A JSON request body that contains the email content.
        required: true
        schema:
          $ref: '#/definitions/EmailCampaignComplete'
      responses:
        '200':
          description: '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.'
          schema:
            $ref: '#/definitions/EmailCampaign'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '409':
          description: Conflict. The resource you are creating or updating conflicts with an existing resource.
        '415':
          description: Unsupported Media Type.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:write
      x-sdk-methodName: createEmailCampaign
      x-ctctmcp-tool-desc: "Use this tool 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. 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 the account.\nBefore creating an email campaign, first retrieve the current account physical mailing address using the getPhysicalAddress tool. If the address is missing or incomplete, do not assume values; ask the user for the missing fields or update the address only with user-provided information.\nCompliance and sender preflight requirements:\n  Before creating an email campaign, the assistant must verify two separate account requirements:\n\n  1. Physical mailing address requirement\n  - First retrieve the current account physical mailing address using the `getPhysicalAddress` tool.\n  - A physical mailing address is required to send emails and displays in the footer of every email sent from the account.\n  - If the address is missing or incomplete, do not assume values.\n  - Ask the user for the missing fields, or update the address only with user-provided information.\n\n  2. Sender email requirement\n  - Then retrieve account email addresses using `retrieveEmailAddresses`.\n  - Do not assume that a confirmed email alone is the best choice for sender headers.\n  - The assistant must verify which confirmed account emails are eligible for campaign headers and should inspect returned email roles.\n  - `from_email` must be a confirmed account email and should prefer an email with the `DEFAULT_FROM` role when available.\n  - `reply_to_email` must be a confirmed account email and should prefer an email with the `REPLY_TO` role when available.\n  - If the same confirmed account email has both roles, it is the preferred default for both fields.\n  - If no role-qualified email exists, the assistant must clearly say so and either ask the user which confirmed account email to use or use a confirmed fallback only if the API allows it and the user accepts.\n  - The assistant must not present sender details as validated until it has actually checked confirmed account emails.\n\nQuality requirement for default output: when the user asks to create an email campaign and does not explicitly request a plain or minimal draft, default to a polished, production-ready HTML marketing email, not a schema-valid stub. Treat any included HTML example as the minimum visual quality bar, not just a valid payload sample.\nStrong preference: generate professionally styled HTML with substantial inline CSS and a clear design system. Prefer: a background color and constrained content container, strong heading hierarchy and readable body typography, intentional spacing and section padding, card or panel structure where appropriate, styled CTA buttons and links, polished image treatment, responsive-friendly table or hybrid email-safe layout patterns, and a coherent visual layout that looks intentionally designed.\nAvoid as the default: barebones bodies with only one or two inline styles, placeholder-looking copy, or a simple heading-plus-paragraph structure when richer HTML is feasible from the information already available.\nUser-discovery requirement: before creating the campaign, strongly prefer gathering enough context to make the email effective. Ask about the users business goal/campaign objective, audience, brand style, and desired call to action when that information is missing and asking is practical. Frame this as improving performance and relevance, not as a blocker. Examples: What is the business goal of this email? Who is the audience? What action do you want readers to take? Do you want it to feel promotional, editorial, or transactional? Are there brand colors, logo, product images, or offers to include? It is very important to personalize the email. If a business website is provided, use it to infer brand style, tone, colors, and destination links. If a logo or image is provided, incorporate it into the email. If neither is provided, clearly label the output as a best-effort draft. If the user has not supplied this context and immediate creation is still necessary, create the best possible polished draft using reasonable assumptions, but optimize for a credible business-ready layout rather than a minimal example.\nBehavioral rule: The assistant should assume the user wants a visually designed email that supports a real business objective. Visual polish does not satisfy this requirement on its own. Unless the user explicitly requests a placeholder, starter draft, mockup, or “just make something,” the assistant must collect the minimum campaign brief — goal, audience, CTA — before creating the campaign. If any of these are missing, ask first. Do not use generic filler strategy or copy as a substitute for the brief.\nTool Requirement: After creating an email campaign, always use the html preview tool get_campaign_html_preview inspect the rendered result. Example HTML below is illustrative, but the assistant should generally produce HTML that is at least as polished as this example unless the user requests otherwise: This is an example of the html content `<html><body style=\"margin:0;padding:0;background-color:#f6f3ee;font-family:Arial,Helvetica,sans-serif;color:#2b2118;\">[[trackingImage]]<table role=\"presentation\" width=\"100%\" cellpadding=\"0\" cellspacing=\"0\" border=\"0\" style=\"background-color:#f6f3ee;margin:0;padding:24px 0;\"><tr><td align=\"center\"><table role=\"presentation\" width=\"600\" cellpadding=\"0\" cellspacing=\"0\" border=\"0\" style=\"width:600px;max-width:600px;background-color:#fffaf3;border-collapse:collapse;border:1px solid #eadfce;\"><tr><td style=\"padding:18px 40px 8px 40px;text-align:center;font-size:12px;letter-spacing:1px;text-transform:uppercase;color:#8a6d4b;\">The crumb report</td></tr><tr><td style=\"padding:0 40px 12px 40px;text-align:center;\"><h1 style=\"margin:0;font-size:34px;line-height:42px;color:#3a2817;\">Big bread news</h1></td></tr><tr><td style=\"padding:0 40px 20px 40px;text-align:center;font-size:17px;line-height:26px;color:#5c4735;\">A very important update from the world of bread, delivered fresh to the bread enjoyer list.</td></tr><tr><td style=\"padding:0 24px 24px 24px;\"><img src=\"https://files.constantcontact.com/bde0a25f401/845f0a70-3610-448e-a493-0aba03ef9e9d.png\" width=\"552\" style=\"display:block;width:100%;max-width:552px;height:auto;border:0;border-radius:12px;\"></td></tr><tr><td style=\"padding:0 40px 10px 40px;font-size:18px;line-height:28px;font-weight:bold;color:#3a2817;\">Today’s loaf highlight</td></tr><tr><td style=\"padding:0 40px 12px 40px;font-size:16px;line-height:26px;color:#4c3b2d;\">This edition celebrates one excellent loaf and the simple joy of admiring good bread. Crispy crust, strong crumb, no notes.</td></tr><tr><td style=\"padding:0 40px 32px 40px;\"><table role=\"presentation\" cellpadding=\"0\" cellspacing=\"0\" border=\"0\"><tr><td style=\"border-radius:999px;border:1px solid #3a2817;padding:12px 22px;font-size:15px;\"><a href=\"https://i.imgur.com/pzNV90U.jpeg\" style=\"color:#3a2817;text-decoration:none;font-weight:bold;\">View the bread</a></td></tr></table></td></tr></table></td></tr></table></body></html>`\n"
      x-ctctmcp-allow: true
  /emails/{campaign_id}:
    get:
      tags:
      - Email Campaigns
      summary: GET Details About a Single Email Campaign
      description: Use this method to get details about a single email campaign and campaign related activities. Details include the email campaign name, current status, create date, last update date, and a list of campaign activities; including the `campaign_activity_id` and `role`.
      operationId: retrieveEmailCampaignUsingGET
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: campaign_id
        in: path
        description: The ID (UUID format) that uniquely identifies this email campaign.
        required: true
        type: string
        x-example: 91569d46-00e4-4a4d-9a4c-d17d98740d04
      responses:
        '200':
          description: Request successful.
          schema:
            $ref: '#/definitions/EmailCampaign'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:read
      x-sdk-methodName: getEmailCampaignById
    delete:
      tags:
      - Email Campaigns
      summary: DELETE an Email Campaign
      description: 'Use this method to delete an email campaign and the email campaign activities associated with the email campaign. You cannot delete an email campaign when it has a `Scheduled` status.


        Constant Contact users can restore deleted email campaigns using the UI.

        '
      operationId: removeEmailCampaignUsingDELETE
      produces:
      - application/json
      parameters:
      - name: campaign_id
        in: path
        description: The unique ID for the email campaign you are deleting.
        required: true
        type: string
        x-example: 91569d46-00e4-4a4d-9a4c-d17d98740d04
      responses:
        '204':
          description: Email campaign successfully deleted. No response body returned.
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:delete
      x-sdk-methodName: deleteEmailCampaign
    patch:
      tags:
      - Email Campaigns
      summary: PATCH (Update) an Email Campaign Name
      description: Use this method to rename an email campaign. The name is not visible to contacts. The name must be unique and cannot exceed 80 characters. You cannot rename email campaigns that have a `Removed` status.
      operationId: renameEmailCampaignUsingPATCH
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: campaign_id
        in: path
        description: The unique identifier for an email campaign.
        required: true
        type: string
        x-example: 91569d46-00e4-4a4d-9a4c-d17d98740d04
      - in: body
        name: body
        description: A JSON payload that contains the new email campaign name.
        required: true
        schema:
          $ref: '#/definitions/EmailCampaignName'
      responses:
        '200':
          description: Request successful.
          schema:
            $ref: '#/definitions/EmailCampaign'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '409':
          description: Conflict. The resource you are creating or updating conflicts with an existing resource.
        '415':
          description: Unsupported Media Type.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:write
      x-ctctmcp-allow: true
      x-sdk-methodName: patchEmailCampaignName
  /emails/campaign_id_xrefs:
    get:
      tags:
      - Email Campaigns
      summary: GET a Collection of V2 and V3 API Email Campaign Identifiers
      description: '<div class="Msg Msg--warning"><p class="note-text">Use this endpoint to migrate your locally stored V2 email campaign data to the new V3 format. Developers are expected to use this endpoint sparingly. This endpoint is NOT intended for regular or repeated use. Constant Contact will eventually deprecate and remove this endpoint.</p></div>


        Use this method to migrate your local V2 API email data to the V3 API format. For each value that you provide in the `v2_email_campaign_ids` query parameter, this method returns the corresponding V3 `campaign_id` and V3 `campaign_activity_id` UUID value. For more information on the changes to the email campaign resource model, see [V3 Email Campaign Resource Changes](/api_guide/v3_v2_email_campaign_deltas.html) in the API guide.

        '
      operationId: retrieveXrefMappingsUsingGET
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: v2_email_campaign_ids
        in: query
        description: Comma separated list of V2 API `campaignId` values. You can enter up to 50 V2 `campaignId` values in each request.
        required: true
        type: string
        maxItems: 50
        format: csv
        x-example: 1100567546598,1604567396117,12002485195578
      responses:
        '200':
          description: Request successful.
          schema:
            $ref: '#/definitions/CrossReferenceResponse'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:read
      x-sdk-methodName: getEmailCampaignXrefs
  /emails/activities/{campaign_activity_id}:
    get:
      tags:
      - Email Campaigns
      summary: GET a Single Email Campaign Activity
      description: 'Use this method to return a specific email campaign activity. Each email campaign activity contains the email content, metadata, and styling information of an email. Email campaign activities can also contain either contact lists or segments. Constant Contact uses this information to determine who to send the email campaign activity to when you schedule it. You cannot get email campaign activities that have a `REMOVED` status.

        '
      operationId: retrieveEmailCampaignActivityUsingGET
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: campaign_activity_id
        in: path
        description: The unique ID for an email campaign activity.
        required: true
        type: string
        x-example: 91569d46-00e4-4a4d-9a4c-d17d98740d04
      - name: include
        in: query
        description: Use the `include` query parameter to enter a comma separated list of additional email campaign activity properties for the V3 API to return. Valid values are `physical_address_in_footer`, `permalink_url`, `html_content`, and `document_properties`.
        required: false
        type: string
        format: csv
        enum:
        - physical_address_in_footer
        - permalink_url
        - html_content
        - document_properties
      responses:
        '200':
          description: Request successful.
          schema:
            $ref: '#/definitions/EmailCampaignActivity'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:read
      x-sdk-methodName: getEmailCampaignActivity
    put:
      tags:
      - Email Campaigns
      summary: PUT (Update) An Email Campaign Activity
      description: 'Use this method to update an email campaign activity by including the complete email campaign activity with your changes in the request body. The request body requires the `from_name`, `from_email`, `reply_to_email`, and `subject` properties.


        You can only update email campaign activities that have the `primary_email` role and that are in `DRAFT` or `Done` status.

        When you use a PUT method to update a resource, the V3 API overwrites any properties that are missing in the request body. However, the V3 API does not overwrite subresources that you omit in the request body or missing properties in subresources. This method considers `physical_address_in_footer`, `document_properties`, `html_content`, and `permalink_url` subresources of the email campaign activity.

        '
      operationId: updateEmailCampaignActivityUsingPUT
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: campaign_activity_id
        in: path
        description: The unique ID for the email campaign activity you are updating.
        required: true
        type: string
        x-example: 91569d46-00e4-4a4d-9a4c-d17d98740d04
      - in: body
        name: body
        description: A request body payload that contains the complete email campaign activity with your changes.
        required: true
        schema:
          $ref: '#/definitions/EmailCampaignActivity'
      responses:
        '200':
          description: Email campaign activity successfully updated.
          schema:
            $ref: '#/definitions/EmailCampaignActivity'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '415':
          description: Unsupported Media Type.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:write
      x-sdk-methodName: updateEmailCampaignActivity
      x-ctctmcp-allow: true
  /emails/activities/{campaign_activity_id}/non_opener_resends:
    get:
      tags:
      - Email Campaigns
      summary: GET Details for a Resend to Non-openers Campaign Activity
      description: Get details about a resend to non-openers campaign activity. If resend activity does not exist for the specified `campaign_activity_id`, an empty list is returned in the results. You can only create one resend activity per email campaign.
      operationId: retrieveResendToNonOpenersUsingGET
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: campaign_activity_id
        in: path
        description: The unique ID for the primary email campaign activity.
        required: true
        type: string
        x-example: 91569d46-00e4-4a4d-9a4c-d17d98740d04
      responses:
        '200':
          description: Request successful.
          schema:
            $ref: '#/definitions/ResendToNonOpeners'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:read
      x-sdk-methodName: getResendEmailCampaign
    post:
      tags:
      - Email Campaigns
      summary: POST a Resend to Non-openers Campaign Activity
      description: "Use this POST method to resend a primary campaign activity to contacts that did not open a campaign activity that has a current `status` of `Draft`, `Scheduled`, or `Done`. You can only create one resend activity per email campaign.\n \n After an email campaign activity is sent to contacts, Constant Contact waits the specified number of `delay_days` or `delay_minutes` (properties are mutually exclusive) before resending to non-openers. If you set both `delay_days` or `delay_minutes`, `delay_minutes` is ignored in the request. You can resend to non-openers a minimum of twelve hours (720 minutes) and a maximum of up to 10 days (or 10 x 1440 minutes) after the initial send date.\n \n "
      operationId: createResendToNonOpenersUsingPOST
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: campaign_activity_id
        in: path
        description: The unique ID for the primary email campaign activity.
        required: true
        type: string
        x-example: 91569d46-00e4-4a4d-9a4c-d17d98740d04
      - in: body
        name: resend_schedule
        description: A JSON request body that specifies when to resend the campaign activity to non-openers.
        required: true
        schema:
          $ref: '#/definitions/ResendToNonOpenersInput'
      responses:
        '201':
          description: Request successful.
          schema:
            $ref: '#/definitions/ResendToNonOpenersObject'
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
        '404':
          description: The requested resource was not found.
        '409':
          description: Conflict. The resource you are creating or updating conflicts with an existing resource.
        '429':
          description: Too many requests. You exceeded the request rate limit.
        '500':
          description: There was a problem with our internal service.
      security:
      - oauth2_implicit:
        - campaign_data
      - oauth2_access_code:
        - campaign_data
      x-authorization-privileges:
      - campaign:send
      x-sdk-methodName: createResendEmailCampaign
  /emails/activities/{campaign_activity_id}/non_opener_resends/{resend_request_id}:
    delete:
      tags:
      - Email Campaigns
      summary: DELETE a Resend to Non Openers Activity
      description: Use this `DELETE` method to delete (unschedule) a resend to non openers activity.
      operationId: deleteResendToNonOpenersUsingDELETE
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: campaign_activity_id
        in: path
        description: The unique ID for the primary email campaign activity.
        required: true
        type: string
        x-example: 91569d46-00e4-4a4d-9a4c-d17d98740d04
      - name: resend_request_id
        in: path
        description: 'The unique ID associated with the resend for the email campaign activity (for example: `389093`). If the email campaign activity is currently in draft status, specify `DRAFT` as the ID.'
        required: true
        type: string
        x-example: '389093'
      responses:
        '204':
          description: Request successful.
        '400':
          description: Bad request. Either the JSON was malformed or there was a data validation error.
        '401':
          description: The Access Token used is invalid.
        '403':
          description: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is dea

# --- truncated at 32 KB (65 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/constant-contact/refs/heads/main/openapi/constant-contact-email-campaigns-api-openapi.yml