MoEngage Data API

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

★ Only Publicly Available OpenAPI DocumentAnalyticsProduct AnalyticsapiKey1 EndpointsREST

For Agents

Stream user events into MoEngage for product analytics and campaign segmentation via a single POST /events endpoint authenticated with workspace headers.

Connect the MoEngage Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MoEngage Data 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 Data API API.

Push a user event such as 'product_viewed' with custom attributes into MoEngage

Stream backend purchase confirmations to MoEngage so they can trigger lifecycle campaigns

Forward server-side conversion events that the SDK cannot capture

Replay historical events into a new MoEngage workspace from a data warehouse

GET STARTED

Start building with MoEngage Data API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for MoEngage Data API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for MoEngage Data API, keeping it validated and agent-ready. The MoEngage Data API ingests user events into the MoEngage customer engagement platform via a single POST /events endpoint, allowing product and analytics teams to stream user actions, attributes, and timestamps for downstream segmentation, campaigns, and analytics. Authentication uses two paired headers — MOE-APPID identifies the workspace and MOE-API-KEY authorises the call.

Use Cases

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

★ Server-Side Event Streaming

Stream purchase confirmations, subscription renewals, and other backend events that the MoEngage mobile and web SDKs cannot see. POST /events accepts a user identifier, event name, attributes, and timestamp, and MoEngage routes them into the same engagement timeline as SDK-captured events. Backend integration is typically a single HTTP client call wrapped in the application's order or billing service.

Send a 'purchase_completed' event for user_id u-12345 with order_total 49.99 USD and timestamp via POST /events

Warehouse-to-MoEngage Backfill

Replay historical event data from BigQuery, Snowflake, or Redshift into MoEngage when migrating from another engagement platform. A scheduled job reads events in batches and POSTs them to /events with the original timestamps, so existing segments rebuild correctly and lifecycle campaigns trigger on real history rather than from migration day forward.

Read the last 90 days of 'order_placed' events from a BigQuery table and POST each one to MoEngage /events preserving the original event timestamp

Agent-Driven Conversion Tracking via Jentic

Use a Jentic-connected agent to stream conversion and intent events from internal tools into MoEngage so growth teams can build segments and triggers without engineering tickets. The agent searches Jentic for the events operation, loads the schema, and posts events with workspace credentials drawn from the vault.

When a sales rep marks a lead as 'closed-won' in the CRM, post a 'deal_closed' event to MoEngage with deal value and product attributes

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for moengage data api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/events

Ingest a user event into MoEngage

POST

/events

Ingest a user event into MoEngage

Why though Jentic?

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

Credential isolation

MOE-APPID and MOE-API-KEY headers are stored encrypted in the Jentic vault (MAXsystem) and injected at execution time. Agents receive scoped execution access — raw workspace credentials never enter the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send a user event to MoEngage') and Jentic returns the POST /events operation with its body schema, so the agent calls it without parsing partial vendor docs.

Time to first call

Direct integration is straightforward — typically half a day for a single ingestion endpoint. Through Jentic: minutes to search, load, and execute the first event.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

MoEngage API

The MoEngage management API manages users, campaigns, and segments while the Data API ingests events.

Use both: the Data API to stream events in, and the MoEngage management API to read campaigns and segments out.

Alternative

Mixpanel API

Mixpanel provides server-side event ingestion plus richer analytics querying for product teams.

Choose Mixpanel when analytics querying is the primary need; choose MoEngage Data API when events drive multichannel campaigns.

Complementary

Segment API

Segment routes a single event stream to many destinations including MoEngage.

Pair with the MoEngage Data API by sending events to Segment first if you want to fan-out the same stream to other tools.

FAQs

Specific to using MoEngage Data API API through Jentic.

Why is there no official OpenAPI spec for MoEngage Data API?

MoEngage does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MoEngage Data API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the MoEngage Data API use?

Every request to POST /events must include both MOE-APPID (the workspace identifier) and MOE-API-KEY (the workspace data API key) as request headers. There is no OAuth flow — these are static workspace credentials. Through Jentic, both headers are stored encrypted in the MAXsystem vault and injected at execution time so the agent never handles them directly.

Can I send historical events with backdated timestamps?

Yes. The /events payload accepts a timestamp field on each event, so server-side jobs can replay historical data into MoEngage with the original event time. This keeps segments and lifecycle campaigns aligned with real user history rather than the ingestion time.

What are the rate limits for the MoEngage Data API?

The OpenAPI spec does not declare a numeric rate limit. MoEngage applies per-workspace ingestion ceilings at the platform level — agents should batch outgoing events, respect 429 responses with exponential backoff, and avoid sending duplicate events with the same user_id and timestamp.

How do I send an event through Jentic?

Run pip install jentic, then search Jentic for 'send a user event to MoEngage'. Jentic returns the POST /events operation with its body schema. Load the schema, pass the user identifier, event name, attributes, and timestamp, then execute. The MOE-APPID and MOE-API-KEY headers are resolved from the vault.

Can I use the MoEngage Data API to read data back?

No. The Data API exposes a single POST /events endpoint for ingestion only. To read campaigns, segments, or user data programmatically, use the separate MoEngage management API (api_slug: moengage) which exposes /campaigns, /segments, and /customer endpoints.