MoEngage API

Name: MoEngage API API
Brand: MoEngage API
Availability: InStock

✓ Official Vendor SpecMarketingMarketing Automationbasic6 EndpointsREST

For Agents

Track customer attributes, ingest events, fetch campaign stats and segments, and process GDPR deletions on the MoEngage engagement platform.

Connect the MoEngage API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MoEngage API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MoEngage API API.

Update customer attributes such as plan, lifecycle stage, or last_active_at

Ingest a user event with custom attributes for campaign triggering

Process a GDPR deletion request for a specific MoEngage customer

List all running and scheduled campaigns in a MoEngage workspace

GET STARTED

Start building with MoEngage API API

Explore with Jentic

View OpenAPI Document

Use for: I need to update a customer's attributes in MoEngage, Send a user event to MoEngage to trigger a campaign, Delete a user from MoEngage to comply with a GDPR request, List all campaigns running in a MoEngage workspace

Not supported: Does not send raw push notifications, build campaigns from scratch, or expose template-level editing — use for customer attribute sync, event ingestion, GDPR deletion, and read-only campaign and segment listing only.

Use Cases

Patterns agents use MoEngage API API for, with concrete tasks.

★ Customer Attribute Sync

Sync user profile changes from a CRM or product backend into MoEngage so segmentation and lifecycle campaigns reflect current state. POST /customer accepts a user identifier and an attributes object — plan, country, last_login_at, lifecycle_stage — and MoEngage merges them into the existing profile. Most teams ship the sync as a webhook handler from the CRM in under a week.

When a CRM contact's plan field changes, post the new value to MoEngage POST /customer with the user_id and updated attribute

Campaign Performance Reporting

Pull delivery, open, and click stats for active MoEngage campaigns into a marketing dashboard or weekly report. GET /campaigns lists every campaign with its metadata, GET /campaigns/{campaignId}/stats returns sent, delivered, opened, and clicked counts. Teams use this to compare cohorts across channels without exporting from the MoEngage UI.

List all campaigns sent in the last 7 days and pull delivery and open rates for each via GET /campaigns/{campaignId}/stats

GDPR Deletion Pipeline

Honour right-to-be-forgotten requests by removing the user record from MoEngage when a customer asks for deletion. POST /delete_user with the user identifier triggers MoEngage's deletion workflow, which removes profile, events, and segment memberships. The endpoint is intended to be wired into the company-wide deletion pipeline alongside CRM and warehouse deletes.

For each entry in the deletion-requests queue, call POST /delete_user with the user_id and log the response status

Agent-Driven Campaign Audit via Jentic

Use a Jentic-connected agent to audit MoEngage campaigns weekly — checking which are still running, comparing delivery rates, and flagging segments with stale rules. The agent searches Jentic for the campaigns and segments operations, loads the schemas, and reads the data with workspace credentials drawn from the vault.

List campaigns and their stats, then return the names of campaigns whose open rate dropped more than 30% week-over-week

Key Endpoints

6 endpoints — moengage is a customer engagement platform that powers cross-channel campaigns across push, email, sms, in-app, and web.

METHOD

PATH

DESCRIPTION

POST

/customer

Update customer attributes

POST

/event

Ingest a user event

POST

/delete_user

Delete a user for GDPR compliance

GET

/campaigns

List all campaigns

GET

/campaigns/{campaignId}/stats

Get delivery and engagement stats for a campaign

GET

/segments

List segments configured for the workspace

POST

/customer

Update customer attributes

POST

/event

Ingest a user event

POST

/delete_user

Delete a user for GDPR compliance

GET

/campaigns

List all campaigns

GET

/campaigns/{campaignId}/stats

Get delivery and engagement stats for a campaign

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MoEngage App ID and API key are stored encrypted in the Jentic vault (MAXsystem) and combined into the HTTP Basic Authorization header at execution time. Agents never handle the raw credentials.

Intent-based discovery

Agents search Jentic by intent (e.g., 'list MoEngage campaigns') and Jentic returns the matching MoEngage operation with its schema, so the agent calls it without browsing docs.

Time to first call

Direct MoEngage integration including auth and workspace setup typically takes 2 to 4 days. Through Jentic: under one hour to search, load, and execute the first call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

MoEngage Data API

The MoEngage Data API is the dedicated high-volume event ingestion endpoint.

Use the Data API for high-volume event streaming; use the MoEngage management API for reading campaigns and managing customer attributes.

Alternative

Braze API

Braze offers a broadly equivalent customer engagement platform with cross-channel campaigns.

Choose Braze for established North American enterprise deployments; choose MoEngage for strong APAC presence and pricing.

Alternative

Klaviyo API

Klaviyo focuses on e-commerce email and SMS marketing automation.

Choose Klaviyo when you sell on Shopify or BigCommerce; choose MoEngage for app-first push and in-app engagement.

FAQs

Specific to using MoEngage API API through Jentic.

What authentication does the MoEngage API use?

MoEngage uses HTTP Basic auth with the workspace App ID as the username and the workspace API key as the password against base URL https://api-01.moengage.com/v1. Through Jentic, both values are stored encrypted in the MAXsystem vault and combined into the Authorization header at execution time so the agent never sees them.

Can I get delivery stats for a specific campaign?

Yes. GET /campaigns/{campaignId}/stats returns delivery, open, click, and other engagement metrics for that campaign. Use GET /campaigns first to enumerate available campaign IDs, then iterate through the IDs to populate a reporting dashboard.

What are the rate limits for the MoEngage API?

The OpenAPI spec does not declare a numeric rate limit. MoEngage applies per-workspace ceilings at the platform level — agents should batch /customer and /event calls, respect 429 responses with exponential backoff, and prefer webhooks where MoEngage offers them rather than tight polling on /campaigns.

How do I list campaigns through Jentic?

Run pip install jentic, then search Jentic for 'list campaigns in MoEngage'. Jentic returns the GET /campaigns operation with its query schema. Load the schema, pass any filters, and execute. The Basic auth header is resolved from the vault.

How do I delete a user from MoEngage for GDPR?

POST /delete_user with the customer identifier in the request body triggers MoEngage's deletion workflow, which removes the profile, associated events, and segment memberships. Wire it into the company-wide deletion pipeline alongside CRM and warehouse deletions to honour right-to-be-forgotten requests end-to-end.

Should I use this API or the MoEngage Data API for sending events?

Use this management API (POST /event) for low-volume events that ride alongside customer attribute and campaign reads. Use the dedicated MoEngage Data API (POST /events under api_slug: data-api) for high-volume server-side ingestion — it is purpose-built for streaming events and uses dedicated MOE-APPID and MOE-API-KEY headers.