API Categories
Data
Create and update users, track events, manage devices, and import data in bulk.
Business Events
Create and trigger business events to power automated campaigns.
Content
Manage templates, content blocks, recommendations, coupons, and catalogs.
Campaigns
Create and manage Push and Email campaigns programmatically.
Segments
Create and manage file-based, filter-based, and cohort-synced user segments.
Subscriptions
Manage email subscriptions and subscription category preferences.
Analytics
Access custom dashboards and fetch the analytics data behind their charts.
Push
Send transactional and targeted push notifications to Android, iOS, and Web.
Cards
Fetch and manage App Inbox cards for users.
Inform
Send transactional alerts across SMS, Email, and Push channels.
Live Activities
Start, update, and end iOS Live Activities via broadcast.
Personalize
Fetch and manage personalized experiences for users.
Message Archival
View and retrieve archived messages.
Data Centers
MoEngage maintains multiple data centers. You are assigned to a specific data center when you sign up. You can identify your data center from your dashboard URL.Choosing a Data Center
If you have data privacy requirements to store user data in a specific geographical region:- US region: Sign up with DC-01 or DC-04
- EU region: Sign up with DC-02
- India region: Sign up with DC-03
- Singapore region: Sign up with DC-05
- Indonesia region: Sign up with DC-06
Base URL
All API requests are made to:{dc} with your data center number (e.g., 01, 02, 03). You can identify your data center from your Dashboard URL.
Each API may have additional path segments (e.g.,
/v1, /core-services/v1). Refer to the specific API documentation for the complete endpoint path.Authentication
All MoEngage API requests require Basic Authentication. To authenticate, you must include a Base64-encoded string of your credentials in the Authorization header of every request. Basic Authentication sends a Base64-encoded string containing your username and password with every API request. It encodes a ‘username:password’ string in Base64 and appends the encoded string with ‘Basic ’. This string is included in the authorization header as shown below:{"Authorization: Basic Base64_ENCODED_WORKSPACEID_APIKEY=="}
Required Headers
The
MOE-APPKEY header (set to your Workspace ID) is required only for File Import APIs and the Test Connection API. It is not required for core Data APIs such as Track User, Get User, Track Event, Merge User, Delete User, and Track Device.Generating Credentials
TheAuthorization header value is a Base64 encoding of workspace_id:api_key.
Getting Your Credentials
- Log in to the MoEngage dashboard.
- Navigate to Settings > Account > APIs.

- Copy your Workspace ID and the relevant API Key.

API Keys by Feature
Different APIs require different API keys from your dashboard:Rate Limits
MoEngage enforces per-workspace rate limits and payload caps on its REST APIs. Requests that exceed a rate limit receive anHTTP 429 response; oversized payloads receive HTTP 413 (or 400). Rate-limited responses include x-ratelimit-limit, x-ratelimit-remaining, and x-ratelimit-reset headers so you can track remaining capacity in real time.
For the full per-endpoint breakdown — rate limits, payload size caps, monitoring headers, and how to request an increase — see Rate Limits.
Error Handling
Most MoEngage APIs return errors in the standard format below.Standard Error Format
Newer v5 APIs, such as Flows, use a different error envelope:
{ response_id, error: { code, message, target, details } }. Refer to the specific API’s reference for its exact error shape.HTTP Status Codes
Key Endpoints Reference
Data
Business Events
Content
Templates
Content Blocks
Recommendations
Coupons
Catalog
Campaigns
Segments
Subscriptions
Push
Cards
Inform
Live Activities
Personalize
Message Archival
Support
Need help with the API?- Support: Contact your Customer Success Manager or raise a support ticket.