# MoEngage (slim)

> MoEngage is a hosted customer engagement platform that stores user profiles and events, builds segments and sends campaigns and flows by push, email, SMS and WhatsApp. Agents reach it through REST APIs and a hosted MCP server.

- Full: https://www.anchorterminal.com/tools/moengage.md (~8,400 tokens) · this version ~2,180 tokens · JSON https://www.anchorterminal.com/tools/moengage.json · canonical https://www.anchorterminal.com/tools/moengage
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-10

**B · 65.2/100 · rank #327 of 950 · #3 in Lifecycle marketing & customer engagement · not agent-ready · confidence medium**


Assessment: MoEngage publishes 36 OpenAPI files covering 140 operations, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 17 August 2026 the Inform API in one data centre accepted requests for about 16 hours without sending the messages.

## Facts

- Kind: HTTP API · vendor: MoEngage, Inc. · category: Lifecycle marketing & customer engagement · legal entity: MoEngage, Inc. · provenance 89/100
- Endpoint: `https://mcp.moengage.com` (HTTP, Streamable HTTP)
- Auth: OAuth or key · pricing: Paid · x402: no · licence: Proprietary service under MoEngage's Terms of Use and a customer agreement
- Probe metrics: not measured yet (probes haven't run)
- API: REST over JSON at `https://api-{dc}.moengage.com`, described in 36 OpenAPI 3 files with 140 operations on 119 paths (79 POST, 31 GET, 16 PUT, 12 PATCH, 2 DELETE). Push uses `pushapi-{dc}`, OAuth `oauth2-{dc}` and Message Archival `archival-{dc}`
- Data centres: DC-01 and DC-04 (United States), DC-02 (EU, Frankfurt), DC-03 (India), DC-05 (Singapore, closed to new signups), DC-06 (Indonesia) and DC-101. Data can't be moved between them
- Resource groups: Users, events, devices and bulk import, file imports, GDPR and CCPA requests, business events, templates for email, push, SMS, in-app and on-site messages, content blocks, catalogues, coupons, recommendations, campaigns, flows, segments, subscriptions, analytics queries, cards, Inform alerts and live activities
- Credentials: HTTP Basic with Workspace ID and API key by default. With the API key dashboard (early access), named keys scoped to API groups, OAuth 2.0 client credentials or AWS STS role ARNs. Regenerating a key invalidates the old one
- Rate limits: Per workspace. Track User 10,000 updates a minute, Track Event 30,000 events a minute, bulk import 60,000 users and 60,000 events a minute, filter segment creation 50 a minute and 1,000 a day, V5 campaign draft creation 5 a minute and 100 a day, file segment operations 10 an hour
- Payload limits: 128 KB a request on the Data APIs, 5 MB on catalogue calls, 150 MB a file for file segments
- Errors: Standard body with `status`, `error.message`, `error.type` and `error.request_id`. V5 APIs return `response_id` and `error.code`, `message`, `target` and `details`. Authentication failures add a `MOENGAGE-AUTH-ERROR-CODE` header such as ER008 for an expired token
- Idempotency: `Idempotency-Key` header on V5 campaign writes and test sends and on flow status changes. Inform treats a repeated `transaction_id` within 5 minutes as a duplicate. None on the Data or segment APIs
- Campaign control: The V5 campaigns API creates, updates, validates and tests Push and Email drafts and pauses, resumes or stops live campaigns. Publishing goes through the V1 `PATCH /core-services/v1/campaigns/{campaign_id}` call or the dashboard
- MCP server: Hosted at https://mcp.moengage.com, OAuth through moeauth.moengage.com. 52 tools in the docs tables. Builds and validates drafts, creates filter segments, reads flows and dashboards, runs five analysis types, and can pause, resume, stop, retire or archive a flow. PII attributes aren't exposed
- SDKs: Android, iOS, Web, React Native, Expo, Flutter, Cordova, Capacitor and Unity client SDKs, each with a dated changelog. No server-side API client library was found
- Status: status.moengage.com on Statuspage, with about 25 components for each data centre and an RSS and Atom history feed
- SLA: 99.9 per cent monthly availability, scheduled downtime 05:00 to 06:00 GMT on Saturdays, backups every 12 hours kept for 3 months
- Certifications: SOC 2 Type 2, ISO 27001:2022, ISO 27701:2019, ISO 22301:2019, CSA STAR Level 1 and HIPAA per the security page. No bug bounty
- Sub-processors: List last modified 1 September 2026 with locations. Amazon Web Services for hosting in each data centre, Google Cloud for PII stores in Qatar and Saudi Arabia, SendGrid for email, and Azure, Google and AWS Bedrock models for the AI functions

- Scores: Reliability 74, Performance pending, Schema & documentation 87, Agent ergonomics 68, Security & auth 69, Payments & pricing 0, Task success pending, Maintenance & community 75, Transparency & trust 75 · total over the 7 assessed categories
- Why: Reliability, Graded on the REST API, with the hosted lines. · Schema & documentation, 36 OpenAPI 3 files are linked from the docs index, with 140 operations on 119 paths and 535 schemas (25). · Agent ergonomics, List and search calls take `page`, `limit` or a cursor, and the MCP server hides tools the user's role can't use, though it documents 52 too… · Security & auth, Keys can be scoped to chosen API groups and individual APIs, regenerated and archived, and can use OAuth 2.0 client credentials with tokens… · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, The Android SDK changelog has an entry dated 9 October 2026 and the Web SDK one dated 8 October (30). · Transparency & trust, Closed service.
- Sources: 28, open questions: 9, both in the full twin
- Capabilities: marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates, notify.push
- JSON: https://www.anchorterminal.com/api/v1/tools/moengage.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/moengage.svg` or a link to https://www.anchorterminal.com/tools/moengage from a page on moengage.com or one of its subdomains, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Take the data centre number from the dashboard URL and call `https://api-{dc}.moengage.com`. Data can't be moved between data centres
2. Send an `Idempotency-Key` header (UUID v4) on V5 campaign writes and test sends, and a `transaction_id` on Inform alerts, which deduplicates for 5 minutes
3. Use internal event and attribute names in segment filters, and run `deep_validate_segment_filters` first. A wrong event name is accepted and the count later fails with no reason
4. Use `in` with a list for text equality in segment filters. `equals` returns a 400 that names no field
5. Reuse an OAuth access token until it nears expiry. The token endpoint allows 5 requests a minute and 30 per 10 minutes for each key

## Connect

```bash
curl --request POST \
  --url https://api-{dc}.moengage.com/v1/customer/YOUR_WORKSPACE_ID \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{ "type": "customer", "customer_id": "user_12345" }'
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/moengage

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Customer.io | BB | 74.5 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates, notify.push | https://www.anchorterminal.com/tools/customer-io.min.md |
| Klaviyo API + MCP | BB | 71.7 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | https://www.anchorterminal.com/tools/klaviyo.min.md |
| Omnisend | B | 64.9 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | https://www.anchorterminal.com/tools/omnisend.min.md |
| Mailchimp Marketing API | C | 57.4 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | https://www.anchorterminal.com/tools/mailchimp-marketing.min.md |
| Iterable | C | 55.2 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | https://www.anchorterminal.com/tools/iterable.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)