MoEngage · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for MoEngage Campaign Stats and Reports Campaign Reports API

2 actions 2 updates phrasing extends openapi/moengage-campaign-reports-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for MoEngage's API. It is a proposal applied on top of the contract, not a document MoEngage publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 2

$.info
$.paths['/campaign_reports/rest_api/{APP_ID}/{FILENAME}'].get

OpenAPI Overlay

Raw ↑ 
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for MoEngage Campaign Stats and Reports Campaign Reports API
  version: 1.0.0
extends: openapi/moengage-campaign-reports-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 1
- target: $.paths['/campaign_reports/rest_api/{APP_ID}/{FILENAME}'].get
  update:
    x-apievangelist-phrasing:
      intent: Download a campaign report file
      effect: read
      questions:
      - How do I download a MoEngage campaign report for a date range?
      - Can I get reports for periodic campaigns as well as one-time ones?
      - What file name do I need to pull a generated campaign report?
      instructions:
      - text: Download campaign report file {FILENAME} for app {APP_ID}.
        slots:
          FILENAME: path.FILENAME
          APP_ID: path.APP_ID
      - text: Fetch the report {FILENAME} from workspace {APP_ID} using signature {Signature}.
        slots:
          FILENAME: path.FILENAME
          APP_ID: path.APP_ID
          Signature: header.Signature
      method: generated
      generated: '2026-10-01'