# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Mailchimp Transactional Exports API
  version: 1.0.0
extends: openapi/mailchimp-exports-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 6
- target: $.paths['/exports/info'].post
  update:
    x-apievangelist-phrasing:
      intent: Check an export job's status and download link
      effect: read
      questions:
      - Is my transactional export job finished, and where do I download the zip?
      - What state is a particular export job in right now?
      instructions:
      - text: Check the status of export job {id} using key {key}.
        slots:
          id: requestBody.id
          key: requestBody.key
      - text: Get the download URL for completed export {id}, API key {key}.
        slots:
          id: requestBody.id
          key: requestBody.key
      method: generated
      generated: '2026-09-26'
- target: $.paths['/exports/list'].post
  update:
    x-apievangelist-phrasing:
      intent: List transactional export jobs
      effect: read
      questions:
      - Which export jobs have I started on my transactional account?
      - Can I see all my past exports and their states?
      instructions:
      - text: List my export jobs using key {key}.
        slots:
          key: requestBody.key
      - text: Show every export I've requested, API key {key}.
        slots:
          key: requestBody.key
      method: generated
      generated: '2026-09-26'
- target: $.paths['/exports/rejects'].post
  update:
    x-apievangelist-phrasing:
      intent: Export the rejection denylist to CSV
      effect: write
      questions:
      - How do I download my full denylist of rejected email addresses?
      - Can I get an email notification when my denylist export is ready?
      instructions:
      - text: Start an export of my rejection denylist using key {key}.
        slots:
          key: requestBody.key
      - text: Export the denylist to rejects.csv and email {notify_email} when done, API key {key}.
        slots:
          notify_email: requestBody.notify_email
          key: requestBody.key
      method: generated
      generated: '2026-09-26'
- target: $.paths['/exports/whitelist'].post
  update:
    x-apievangelist-phrasing:
      intent: Export the allowlist (legacy whitelist endpoint)
      effect: write
      questions:
      - Is the older exports/whitelist call still available for exporting my allowlist?
      - Can I keep using the legacy whitelist export endpoint in existing code?
      instructions:
      - text: Export my allowlist via the legacy whitelist endpoint using key {key}.
        slots:
          key: requestBody.key
      - text: Call the old whitelist export and notify {notify_email}, API key {key}.
        slots:
          notify_email: requestBody.notify_email
          key: requestBody.key
      method: generated
      generated: '2026-09-26'
- target: $.paths['/exports/allowlist'].post
  update:
    x-apievangelist-phrasing:
      intent: Export the rejection allowlist to CSV
      effect: write
      questions:
      - How do I download a CSV of every address on my rejection allowlist?
      - What fields are included when I export the allowlist?
      instructions:
      - text: Start an allowlist export to allowlist.csv using key {key}.
        slots:
          key: requestBody.key
      - text: Export my current allowlist and email {notify_email} when it's ready, API key {key}.
        slots:
          notify_email: requestBody.notify_email
          key: requestBody.key
      method: generated
      generated: '2026-09-26'
- target: $.paths['/exports/activity'].post
  update:
    x-apievangelist-phrasing:
      intent: Export sending activity history to CSV
      effect: write
      questions:
      - Can I export my transactional sending history for a date range?
      - Is it possible to limit an activity export to certain senders, tags or message states?
      instructions:
      - text: Export activity from {date_from} to {date_to} using key {key}.
        slots:
          date_from: requestBody.date_from
          date_to: requestBody.date_to
          key: requestBody.key
      - text: Export activity history for tags {tags} sent by {senders} and notify {notify_email}, key {key}.
        slots:
          tags: requestBody.tags
          senders: requestBody.senders
          notify_email: requestBody.notify_email
          key: requestBody.key
      method: generated
      generated: '2026-09-26'