MoEngage Update Campaigns API

The Update Campaigns API from MoEngage — 5 operation(s) for update campaigns.

Business capability
Digital Marketing Management BC-400.60

Operations 5

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

PATCH /v5/campaigns/{campaign_id} Edit a campaign draft (V5) · Update Campaign (V5) #
Ask an LLM
“How do I change the content or audience of a draft campaign with the V5 API?”
“Can I update just one component of a draft campaign?”
Tell an agent
Update draft campaign {campaign_id}'s content.
Change the audience on V5 draft {campaign_id}.
PATCH /v5/campaigns/{campaign_id}/status Pause, resume or stop a published campaign (V5) · Update Campaign Status (V5) #
Ask an LLM
“How do I pause a published email campaign with the V5 API?”
“Which state transitions can I apply to a live V5 campaign?”
Tell an agent destructive · confirm first
Apply {action} to published campaign {campaign_id}.
Stop V5 campaign {campaign_id}.
PATCH /campaigns/{campaign_id} Update an API-created campaign (legacy) · Update Campaign (V1 — Legacy) #
Ask an LLM
“How do I update a campaign I created through the API on the legacy endpoint?”
“Can I edit dashboard-created campaigns via the older update endpoint?”
Tell an agent
Update legacy campaign {campaign_id}.
Edit the content of API-created campaign {campaign_id} on the older endpoint.
POST /campaigns/status Stop, pause or resume several campaigns (legacy) · Change Campaign Status #
Ask an LLM
“Can I pause several API-created campaigns at once?”
“How do I resume campaigns in bulk on the legacy status endpoint?”
Tell an agent destructive · confirm first
Apply {action} to campaigns {campaign_ids}, request {request_id}.
Resume legacy campaigns {campaign_ids} with action {action} and request {request_id}.
PUT /global-control-group/users Add or remove users in the Global Control Group · Update Global Control Group #
Ask an LLM
“How do I add users to the Global Control Group so they're held out of campaigns?”
“Can I remove a list of users from the global control group with a CSV?”
Tell an agent
{action_type} the users in {file_url} to the Global Control Group, by {updated_by}, request {request_id}.
Remove users listed in {file_url} from the global control group as {updated_by}, action {action_type}, request {request_id}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/moengage-update-campaigns-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

moengage-update-campaigns-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Moengage Update Campaigns API
  version: '2025-11-20'
  contact:
    name: MoEngage Developer Team
    email: support@moengage.com
    url: https://developers.moengage.com
  description: 'Operations tagged Update Campaigns across 2 of this provider''s published API definitions: moengage-campaign-draft-openapi.yml, moengage-campaigns-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api-{dc}.moengage.com/
  description: MoEngage Campaigns API Server
  variables:
    dc:
      default: '01'
      description: Data center (DC) segment in the hostname. Replace `OX` with your workspace DC (01–06 or 101). See [Data centers](/api/introduction#data-centers).
- url: https://api-{dc}.moengage.com/core-services/v1
  description: MoEngage Campaigns API Server
  variables:
    dc:
      default: '01'
      description: The ‘dc’ in the API Endpoint URL refers to the MoEngage Data Center (DC). MoEngage hosts each customer in a different DC. You can find your DC number and replace the value of ‘dc’ in the URL by referring to the DC and API endpoint mapping [here](/api/introduction#data-centers). Your MoEngage Data Center (DC) can be 01, 02, 03, 04, 05, 06, or 101.
security:
- BasicAuth: []
tags:


# --- truncated at 32 KB (210 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/moengage/refs/heads/main/openapi/moengage-update-campaigns-api-openapi.yml