Mailchimp Rejects API

Manage the rejection blacklist, which prevents delivery to addresses that have previously bounced or been reported as spam.

Documentation

Specifications

Schemas & Data

Other Resources

OpenAPI Specification

mailchimp-rejects-api-openapi.yml Raw ↑
swagger: '2.0'
info:
  version: 3.0.55
  title: Mailchimp Marketing Abuse Rejects API
  contact:
    name: Mailchimp API Support
    email: apihelp@mailchimp.com
  x-permalink: https://github.com/mailchimp/mailchimp-client-lib-codegen/blob/main/spec/marketing.json
  description: '

    The Mailchimp Marketing API provides programmatic access to Mailchimp data

    and functionality, allowing developers to build custom features to do

    things like sync email activity and campaign analytics with their

    database, manage audiences and campaigns, and more.'
host: server.api.mailchimp.com
basePath: /3.0
schemes:
- https
consumes:
- application/json
produces:
- application/json
- application/problem+json
security:
- basicAuth: []
tags:
- name: Rejects
  description: Manage the rejection blacklist, which prevents delivery to addresses that have previously bounced or been reported as spam.
paths:
  /rejects/list:
    post:
      operationId: postRejectsList
      summary: Mailchimp List Rejections
      description: Retrieve all entries in the rejection blacklist. These are email addresses that have previously hard-bounced or been reported as spam, and will be automatically rejected.
      tags:
      - Rejects
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - key
              properties:
                key:
                  type: string
                  description: A valid Mandrill API key.
                email:
                  type: string
                  format: email
                  description: Optional email address or prefix to filter results.
                include_expired:
                  type: boolean
                  default: false
                  description: Whether to include expired rejections.
                subaccount:
                  type: string
                  description: Optional subaccount ID to restrict results.
            examples:
              PostrejectslistRequestExample:
                summary: Default postRejectsList request
                x-microcks-default: true
                value:
                  key: example_value
                  email: user@example.com
                  include_expired: true
                  subaccount: example_value
      responses:
        '200':
          description: An array of rejection entries.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/RejectEntry'
              examples:
                Postrejectslist200Example:
                  summary: Default postRejectsList 200 response
                  x-microcks-default: true
                  value:
                  - email: user@example.com
                    reason: hard-bounce
                    detail: example_value
                    created_at: '2026-01-15T10:30:00Z'
                    last_event_at: '2026-01-15T10:30:00Z'
                    expires_at: '2026-01-15T10:30:00Z'
                    expired: true
                    subaccount: example_value
                    sender:
                      address: example_value
                      created_at: '2026-01-15T10:30:00Z'
                      sent: 10
                      hard_bounces: 10
                      soft_bounces: 10
                      rejects: 10
                      complaints: 10
                      unsubs: 10
                      opens: 10
                      clicks: 10
        '400':
          $ref: '#/components/responses/ValidationError'
        '401':
          $ref: '#/components/responses/InvalidKeyError'
        '500':
          $ref: '#/components/responses/GeneralError'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
  /rejects/add:
    post:
      operationId: postRejectsAdd
      summary: Mailchimp Add a Rejection
      description: Manually add an email address to the rejection blacklist. Messages to this address will be rejected.
      tags:
      - Rejects
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - key
              - email
              properties:
                key:
                  type: string
                  description: A valid Mandrill API key.
                email:
                  type: string
                  format: email
                  description: The email address to block.
                comment:
                  type: string
                  description: An optional comment about why the address was blacklisted.
                subaccount:
                  type: string
                  description: Optional subaccount to restrict the rejection to.
            examples:
              PostrejectsaddRequestExample:
                summary: Default postRejectsAdd request
                x-microcks-default: true
                value:
                  key: example_value
                  email: user@example.com
                  comment: example_value
                  subaccount: example_value
      responses:
        '200':
          description: Details about the newly added rejection.
          content:
            application/json:
              schema:
                type: object
                properties:
                  email:
                    type: string
                    description: The email address that was added.
                  added:
                    type: boolean
                    description: Whether the address was added to the blacklist.
              examples:
                Postrejectsadd200Example:
                  summary: Default postRejectsAdd 200 response
                  x-microcks-default: true
                  value:
                    email: user@example.com
                    added: true
        '400':
          $ref: '#/components/responses/ValidationError'
        '401':
          $ref: '#/components/responses/InvalidKeyError'
        '500':
          $ref: '#/components/responses/GeneralError'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
  /rejects/delete:
    post:
      operationId: postRejectsDelete
      summary: Mailchimp Delete a Rejection
      description: Remove an email address from the rejection blacklist, allowing messages to be delivered to it again.
      tags:
      - Rejects
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - key
              - email
              properties:
                key:
                  type: string
                  description: A valid Mandrill API key.
                email:
                  type: string
                  format: email
                  description: The email address to remove from the blacklist.
                subaccount:
                  type: string
                  description: Optional subaccount that the rejection applies to.
            examples:
              PostrejectsdeleteRequestExample:
                summary: Default postRejectsDelete request
                x-microcks-default: true
                value:
                  key: example_value
                  email: user@example.com
                  subaccount: example_value
      responses:
        '200':
          description: Details about the removed rejection.
          content:
            application/json:
              schema:
                type: object
                properties:
                  email:
                    type: string
                    description: The email address that was removed.
                  deleted:
                    type: boolean
                    description: Whether the address was removed from the blacklist.
                  subaccount:
                    type: string
                    description: The subaccount blacklist the deletion applied to.
              examples:
                Postrejectsdelete200Example:
                  summary: Default postRejectsDelete 200 response
                  x-microcks-default: true
                  value:
                    email: user@example.com
                    deleted: true
                    subaccount: example_value
        '400':
          $ref: '#/components/responses/ValidationError'
        '401':
          $ref: '#/components/responses/InvalidKeyError'
        '500':
          $ref: '#/components/responses/GeneralError'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
components:
  responses:
    ValidationError:
      description: The request parameters were invalid.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    GeneralError:
      description: An unexpected error occurred on the server.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    InvalidKeyError:
      description: The provided API key is not valid.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    RejectEntry:
      type: object
      description: An entry in the rejection blacklist.
      properties:
        email:
          type: string
          format: email
          description: The rejected email address.
          example: user@example.com
        reason:
          type: string
          enum:
          - hard-bounce
          - soft-bounce
          - spam
          - unsub
          - custom
          description: The reason the address is on the blacklist.
          example: hard-bounce
        detail:
          type: string
          description: Extended details about the rejection.
          example: example_value
        created_at:
          type: string
          format: date-time
          description: When the entry was added to the blacklist.
          example: '2026-01-15T10:30:00Z'
        last_event_at:
          type: string
          format: date-time
          description: When the last event occurred for this address.
          example: '2026-01-15T10:30:00Z'
        expires_at:
          type: string
          format: date-time
          description: When the rejection expires (if applicable).
          example: '2026-01-15T10:30:00Z'
        expired:
          type: boolean
          description: Whether the rejection has expired.
          example: true
        subaccount:
          type: string
          description: The subaccount this rejection applies to, if any.
          example: example_value
        sender:
          type: object
          properties:
            address:
              type: string
              format: email
            created_at:
              type: string
              format: date-time
            sent:
              type: integer
            hard_bounces:
              type: integer
            soft_bounces:
              type: integer
            rejects:
              type: integer
            complaints:
              type: integer
            unsubs:
              type: integer
            opens:
              type: integer
            clicks:
              type: integer
          description: Sender statistics associated with the rejection.
          example: example_value
    Error:
      type: object
      description: A standard error response from the Mandrill API.
      properties:
        status:
          type: string
          enum:
          - error
          description: Always "error" for error responses.
          example: error
        code:
          type: integer
          description: The numeric error code.
          example: 10
        name:
          type: string
          description: The name/type of the error (e.g., Invalid_Key, ValidationError).
          example: Example Title
        message:
          type: string
          description: A human-readable description of the error.
          example: example_value
securityDefinitions:
  basicAuth:
    type: basic
externalDocs:
  description: Learn more with the full Mailchimp API documentation.
  url: https://mailchimp.com/developer/marketing/
x-doc-structure:
  resources:
    root:
      title: API Root
      description: The API root resource links to all other resources available in the API. Calling the root directory also returns details about the Mailchimp user account.
      paths:
      - /
      subResources: []
    chimp-chatter:
      title: Chimp Chatter Activity
      description: Get the latest Chimp Chatter activity from your account.
      paths:
      - /activity-feed/chimp-chatter
    authorized-apps:
      title: Authorized Apps
      description: Manage registered, connected apps for your Mailchimp account with the Authorized Apps endpoints.
      paths:
      - /authorized-apps
      - /authorized-apps/{app_id}
    automation:
      title: Automations
      description: Mailchimp's classic automations feature lets you build a series of emails that send to subscribers when triggered by a specific date, activity, or event. Use the API to manage Automation workflows, emails, and queues. Does not include Customer Journeys.
      paths:
      - /automations
      - /automations/{workflow_id}
      - /automations/{workflow_id}/actions/start-all-emails
      - /automations/{workflow_id}/actions/pause-all-emails
      - /automations/{workflow_id}/actions/archive
      subResources:
      - automation-email
      - automation-removed-subscribers
    automation-email:
      title: Emails
      description: Manage individual emails in a classic automation workflow.
      paths:
      - /automations/{workflow_id}/emails
      - /automations/{workflow_id}/emails/{workflow_email_id}
      - /automations/{workflow_id}/emails/{workflow_email_id}/actions/pause
      - /automations/{workflow_id}/emails/{workflow_email_id}/actions/start
      subResources:
      - automation-email-queue
    automation-email-queue:
      title: Queue
      description: Manage list member queues for classic automation emails.
      paths:
      - /automations/{workflow_id}/emails/{workflow_email_id}/queue
      - /automations/{workflow_id}/emails/{workflow_email_id}/queue/{subscriber_hash}
      subResources: []
    automation-removed-subscribers:
      title: Removed Subscribers
      description: Remove subscribers from a classic automation workflow.
      paths:
      - /automations/{workflow_id}/removed-subscribers
      - /automations/{workflow_id}/removed-subscribers/{subscriber_hash}
      subResources: []
    batch-operations:
      title: Batch Operations
      description: Use batch operations to complete multiple operations with a single call.
      paths:
      - /batches
      - /batches/{batch_id}
    batch-webhooks:
      title: Batch Webhooks
      description: 'Manage webhooks for batch operations. '
      paths:
      - /batch-webhooks
      - /batch-webhooks/{batch_webhook_id}
    account-exports:
      title: Account Exports
      description: Generate a new export or download a finished export.
      paths:
      - /account-exports
      - /account-exports/{export_id}
    campaigns:
      title: Campaigns
      description: Campaigns are how you send emails to your Mailchimp list. Use the Campaigns API calls to manage campaigns in your Mailchimp account.
      paths:
      - /campaigns
      - /campaigns/{campaign_id}
      - /campaigns/{campaign_id}/actions/cancel-send
      - /campaigns/{campaign_id}/actions/send
      - /campaigns/{campaign_id}/actions/schedule
      - /campaigns/{campaign_id}/actions/unschedule
      - /campaigns/{campaign_id}/actions/pause
      - /campaigns/{campaign_id}/actions/resume
      - /campaigns/{campaign_id}/actions/replicate
      - /campaigns/{campaign_id}/actions/test
      - /campaigns/{campaign_id}/actions/create-resend
      subResources:
      - campaign-feedback
      - campaign-checklist
      - campaign-content
    campaign-feedback:
      title: Feedback
      description: Post comments, reply to team feedback, and send test emails while you're working together on a Mailchimp campaign.
      paths:
      - /campaigns/{campaign_id}/feedback
      - /campaigns/{campaign_id}/feedback/{feedback_id}
    campaign-checklist:
      title: Send Checklist
      description: Review the send checklist for your campaign, and resolve any issues before sending.
      paths:
      - /campaigns/{campaign_id}/send-checklist
    campaign-content:
      title: Content
      description: Manage the HTML, plain-text, and template content for your Mailchimp campaigns.
      paths:
      - /campaigns/{campaign_id}/content
    connected-sites:
      title: Connected Sites
      description: Manage sites you've connected to your Mailchimp account.
      paths:
      - /connected-sites
      - /connected-sites/{connected_site_id}
      - /connected-sites/{connected_site_id}/actions/verify-script-installation
    conversations:
      title: Conversations
      description: Conversation tracking lets you view subscribers' replies to your campaigns in your Mailchimp account.
      paths:
      - /conversations
      - /conversations/{conversation_id}
      subResources:
      - conversation-messages
    conversation-messages:
      title: Messages
      description: Manage messages in a specific campaign conversation.
      paths:
      - /conversations/{conversation_id}/messages
      - /conversations/{conversation_id}/messages/{message_id}
    customer-journeys-journeys-steps-actions:
      title: Customer Journeys
      description: Manage Customer Journey automated workflows
      paths:
      - /customer-journeys/journeys/{journey_id}/steps/{step_id}/actions/trigger
      subResources: []
    file-manager:
      title: File Manager
      description: Manage files for your Mailchimp account. The File Manager is a place to store images, documents, and other files you include or link to in your campaigns, templates, or signup forms.
      paths: []
      subResources:
      - file-manager-folders
      - file-manager-files
    file-manager-folders:
      title: File Manager Folders
      description: Manage specific folders in the File Manager for your Mailchimp account.
      paths:
      - /file-manager/folders
      - /file-manager/folders/{folder_id}
      subResources:
      - file-manager-folders-files
    file-manager-files:
      title: File Manager Files
      description: Manage specific files in the File Manager for your Mailchimp account.
      paths:
      - /file-manager/files
      - /file-manager/files/{file_id}
    file-manager-folders-files:
      title: Files in Folder
      description: Manage specific files in a folder.
      paths:
      - /file-manager/folders/{folder_id}/files
    landing-pages:
      title: Landing Pages
      description: Manage your Landing Pages, including publishing and unpublishing.
      paths:
      - /landing-pages
      - /landing-pages/{page_id}
      - /landing-pages/{page_id}/actions/publish
      - /landing-pages/{page_id}/actions/unpublish
      subResources:
      - landing-pages_content
    landing-pages_content:
      title: Content
      description: The HTML content for your Mailchimp landing pages.
      paths:
      - /landing-pages/{page_id}/content
    lists:
      title: Lists/Audiences
      description: Your Mailchimp list, also known as your audience, is where you store and manage all of your contacts.
      paths:
      - /lists
      - /lists/{list_id}
      subResources:
      - interest-categories
      - list-segments
      - abuse-reports
      - list-activity
      - list-clients
      - list-growth-history
      - list-imports
      - list-members
      - list-merges
      - list-webhooks
      - list-signup-forms
      - list-locations
      - lists-tags-search
      - prebuilt-segments
      - list-preview-segment
      - list-surveys
      - list-sms-program
    list-members:
      title: Members
      description: Manage members of a specific Mailchimp list, including currently subscribed, unsubscribed, and bounced members.
      paths:
      - /lists/{list_id}/members
      - /lists/{list_id}/members/{subscriber_hash}
      - /lists/{list_id}/members/{subscriber_hash}/actions/delete-permanent
      subResources:
      - list-member-activity
      - list-member-activity-feed
      - list-member-goal
      - list-member-notes
      - list-member-tags
      - list-member-events
    list-merges:
      title: Merge Fields
      description: Manage merge fields for an audience. See [Merge Field documentation](https://mailchimp.com/developer/marketing/docs/merge-fields/) for more.
      paths:
      - /lists/{list_id}/merge-fields
      - /lists/{list_id}/merge-fields/{merge_id}
      subResources: []
    abuse-reports:
      title: Abuse Reports
      description: Manage abuse complaints for a specific list. An abuse complaint occurs when your recipient reports an email as spam in their mail program.
      paths:
      - /lists/{list_id}/abuse-reports
      - /lists/{list_id}/abuse-reports/{report_id}
    list-activity:
      title: Activity
      description: Get recent daily, aggregated activity stats for your list. For example, view unsubscribes, signups, total emails sent, opens, clicks, and more, for up to 180 days.
      paths:
      - /lists/{list_id}/activity
    list-clients:
      title: Clients
      description: Get information about the most popular email clients for subscribers in a specific Mailchimp list.
      paths:
      - /lists/{list_id}/clients
    list-growth-history:
      title: Growth History
      description: View a summary of the month-by-month growth activity for a specific list.
      paths:
      - /lists/{list_id}/growth-history
      - /lists/{list_id}/growth-history/{month}
    list-webhooks:
      title: Webhooks
      description: Manage webhooks for a specific Mailchimp list.
      paths:
      - /lists/{list_id}/webhooks
      - /lists/{list_id}/webhooks/{webhook_id}
    list-surveys:
      title: Surveys
      description: Get survey data for this audience.
      paths:
      - /lists/{list_id}/surveys
      - /lists/{list_id}/surveys/{survey_id}
      - /lists/{list_id}/surveys/{survey_id}/actions/publish
      - /lists/{list_id}/surveys/{survey_id}/actions/unpublish
      - /lists/{list_id}/surveys/{survey_id}/actions/create-email
    interest-categories:
      title: Interest Categories
      description: Manage interest categories for a specific list. Interest categories organize interests, which are used to group subscribers based on their preferences. These correspond to 'group titles' in the Mailchimp application.
      paths:
      - /lists/{list_id}/interest-categories
      - /lists/{list_id}/interest-categories/{interest_category_id}
      subResources:
      - interests
    interests:
      title: Interests
      description: Manage interests for a specific Mailchimp list. Assign subscribers to interests to group them together. Interests are referred to as 'group names' in the Mailchimp application.
      paths:
      - /lists/{list_id}/interest-categories/{interest_category_id}/interests
      - /lists/{list_id}/interest-categories/{interest_category_id}/interests/{interest_id}
    lists-tags-search:
      title: Tag Search
      description: Search for tags on a list by name.
      paths:
      - /lists/{list_id}/tag-search
    list-segments:
      title: Segments
      description: Manage segments and tags for a specific Mailchimp list. A segment is a section of your list that includes only those subscribers who share specific common field information. Tags are labels you create to help organize your contacts.
      paths:
      - /lists/{list_id}/segments
      - /lists/{list_id}/segments/{segment_id}
      subResources:
      - list-segment-members
    list-segment-members:
      title: Segment Members
      description: Manage list members in a saved segment.
      paths:
      - /lists/{list_id}/segments/{segment_id}/members
      - /lists/{list_id}/segments/{segment_id}/members/{subscriber_hash}
    list-member-activity:
      title: Member Activity
      description: Get details about a subscriber's recent activity. Use the new activity-feed endpoint to access more events for a given contact.
      paths:
      - /lists/{list_id}/members/{subscriber_hash}/activity
    list-member-activity-feed:
      title: Member Activity Feed
      description: Get details about a subscriber's recent activity.
      paths:
      - /lists/{list_id}/members/{subscriber_hash}/activity-feed
    list-member-goal:
      title: Member Goals
      description: Get information about recent goal events for a specific list member.
      paths:
      - /lists/{list_id}/members/{subscriber_hash}/goals
    list-member-notes:
      title: Member Notes
      description: Retrieve recent notes for a specific list member.
      paths:
      - /lists/{list_id}/members/{subscriber_hash}/notes
      - /lists/{list_id}/members/{subscriber_hash}/notes/{note_id}
    list-member-tags:
      title: Member Tags
      description: Manage all the tags that have been assigned to a contact.
      paths:
      - /lists/{list_id}/members/{subscriber_hash}/tags
    list-member-events:
      title: Events
      description: 'Use the Events endpoint to collect website or in-app actions and trigger targeted automations. '
      paths:
      - /lists/{list_id}/members/{subscriber_hash}/events
    list-signup-forms:
      title: Signup Forms
      description: Manage list signup forms.
      paths:
      - /lists/{list_id}/signup-forms
    list-locations:
      title: Locations
      description: Get the locations (countries) that the list's subscribers have been tagged to based on geocoding their IP address.
      paths:
      - /lists/{list_id}/locations
    reports:
      title: Reports
      description: 'Manage campaign reports for your Mailchimp account. All Reports endpoints are read-only. Mailchimp''s campaign and automation reports analyze clicks, opens, subscribers'' social activity, e-commerce data, and more. Note: Campaign IDs for A/B Testing Campaigns are available through the Campaign API Endpoint''s Read method.'
      paths:
      - /reports
      - /reports/{campaign_id}
      subResources:
      - campaign-abuse
      - campaign-advice
      - click-reports
      - domain-performance-reports
      - eepurl-reports
      - email-activity-reports
      - location-reports
      - sent-to-reports
      - sub-reports
      - unsub-reports
      - open-reports
      - campaign-ecommerce-product-activity
    campaign-abuse:
      title: Campaign Abuse
      description: Get information about campaign abuse complaints.
      paths:
      - /reports/{campaign_id}/abuse-reports
      - /reports/{campaign_id}/abuse-reports/{report_id}
    campaign-advice:
      title: Campaign Advice
      description: Get recent feedback based on a campaign's statistics.
      paths:
      - /reports/{campaign_id}/advice
    open-reports:
      title: Campaign Open Reports
      description: 'Get a detailed report about any emails in a specific campaign that were opened by the recipient. '
      paths:
      - /reports/{campaign_id}/open-details
      - /reports/{campaign_id}/open-details/{subscriber_hash}
    click-reports:
      title: Click Reports
      description: Get detailed information about links clicked in campaigns.
      paths:
      - /reports/{campaign_id}/click-details
      - /reports/{campaign_id}/click-details/{link_id}
      subResources:
      - link-clickers
    campaign-ecommerce-product-activity:
      title: Ecommerce Product Activity
      description: Ecommerce product activity report for a campaign.
      paths:
      - /reports/{campaign_id}/ecommerce-product-activity
    link-clickers:
      title: Click Reports Members
      description: Get information about specific subscribers who clicked on links in a campaign.
      paths:
      - /reports/{campaign_id}/click-details/{link_id}/members
      - /reports/{campaign_id}/click-details/{link_id}/members/{subscriber_hash}
    domain-performance-reports:
      title: Domain Performance
      description: Get statistics for the top-performing domains from a campaign.
      paths:
      - /reports/{campaign_id}/domain-performance
    eepurl-reports:
      title: EepURL Reports
      description: Get a summary of social activity for the campaign, tracked by EepURL.
      paths:
      - /reports/{campaign_id}/eepurl
    email-activity-reports:
      title: Email Activity
      description: Get list member activity for a specific campaign.
      paths:
      - /reports/{campaign_id}/email-activity
      - /reports/{campaign_id}/email-activity/{subscriber_hash}
    location-reports:
      title: Location
      description: Get top open locations for a specific campaign.
      paths:
      - /reports/{campaign_id}/locations
    sent-to-reports:
      title: Sent To
      description: Get details about campaign recipients.
      paths:
      - /reports/{campaign_id}/sent-to
      - /reports/{campaign_id}/sent-to/{subscriber_hash}
    sub-reports:
      title: Sub-Reports
      description: A list of reports for child campaigns of a specific parent campaign. For example, use this endpoint to view Multivariate, RSS, and A/B Testing Campaign reports.
      paths:
      - /reports/{campaign_id}/sub-reports
    unsub-reports:
      title: Unsubscribes
      description: Get information about list members who unsubscribed from a specific campaign.
      paths:
      - /reports/{campaign_id}/unsubscribed
      - /reports/{campaign_id}/unsubscribed/{subscriber_hash}
    templates:
      title: Templates
      description: 'Manage your Mailchimp templates. A template is an HTML file used to create the layout and basic design for a campaign. '
      paths:
      - /templates
      - /templates/{template_id}
      subResources:
      - template-default-content
    template-default-content:
      title: Default Content
      description: Manage the default content for a Mailchimp template.
      paths:
      - /templates/{template_id}/default-content
    template-folders:
      title: Template Folders
      description: Organize your templates using folders.
      paths:
      - /template-folders
      - /template-folders/{folder_id}
    campaign-folders:
      title: Campaign Folders
      description: Organize your campaigns using folders.
      paths:
      - /campaign-folders
      - /campaign-folders/{folder_id}
    ecommerce-stores:
      title: E-commerce Stores
      description: Connect your E-commerce Store to Mailchimp to take advantage of powerful reporting and personalization features and to learn more about your customers.
      paths:
      - /ecommerce/stores
      - /ecommerce/stores/{store_id}
      subResources:
      - ecommerce-customers
      - ecommerce-orders
      - ecommerce-products
      - ecommerce-carts
      - ecommerce-promo-rules
    ecommerce-customers:
      title: Customers
      description: Add Customers to your Store to track their orders and to view E-Commerce Data for your Mailchimp lists and campaigns. Each Customer is connected to a Mailchimp list member, so adding a Customer can also add or update a list member.
      paths:
      - /ecommerce/stores/{store_id}/customers
      - /ecommerce/stores/{store_id}/customers/{customer_id}
    ecommerce-promo-rules:
      title: Promo Rules
      description: Promo Rules help you create promo codes for your campaigns. Promo Rules define generic information about promo codes like expiration time, start time, amount of discount being offered etc. For a given promo rule you can define if it's a percentage discount or a fixed amount and if it applies for the order as a whole or if it's per item or free shipping. You can then create promo codes for this price rule. Promo codes contain the actual code that is applied at checkout along with some other information. Price Rules have one to many relationship with promo codes.
      paths:
      - /ecommerce/stores/{store_id}/promo-rules
      - /ecommerce/stores/{store_id}/promo-rules/{promo_rule_id}
      subResources:
      - ecommerce-promo-codes
    ecommerce-promo-codes:
      title: Promo Codes
      description: Promo codes can be created for a given price rule. All the promo codes under a price rule share the generic information defined for that rule like the amount, type, expiration date etc. Promo code defines the mo

# --- truncated at 32 KB (37 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/mailchimp/refs/heads/main/openapi/mailchimp-rejects-api-openapi.yml