See the below table for a list of MoEngage APIs.

For our customers in EU Region, please navigate to this table - List of EU APIs.

The <APP ID> for your moengage account is available here: (Settings > App Settings > Account Settings > APP ID).

Note: We have updated the List of APIs on 4th December 2018 but we are continuing to support the older APIs as of now. The older APIs listed below will be deprecated soon. We strongly recommend all MoEngage users to migrate to the new APIs listed in the previous table.

If you are using the older APIs, app_id is a required param
app_id: Get the APP ID from the MoEngage dashboard under following path: (Settings > App Settings > Account Settings > APP ID).

The below table lists the APIs available for EU Region -

If you are using the APIs for EU Region, please ensure that you are passing app_id as a parameter.
app_id: Get the APP ID from the MoEngage dashboard under following path: (Settings > App Settings > Account Settings > APP ID).

• Authentication
• Content-Type Header
• MOE-APPKEY

Data APIs use Basic authentication to control access to your data.

Basic authentication sends a Base64-encoded string that contains a username and password for your API requests. username and password are available under following path: (Settings > APIs > DATA API Settings) as shown below.

For first time, hit the Generate Key and then save on Data APIs settings page.
User name - DATA API ID
Password - DATA API KEY

Basic Authentication encodes a 'username:password' using base64 and prepends it with the string 'Basic '. This is passed in the authorization header as follows
{"Authorization": "Basic bmF2ZWVua3VtYXI6bW9lbmdhZ2U="}

To send a request using a client (as Postman), Authentication can be done in following way:

To send data to Data APIs, Content-Type header must be set to 'application/json' as follows
{"Content-Type": "application/json"}

To send data via Data APIs, MOE-APPKEY header must be set to <APP ID> which is available here: (Settings > App Settings > Account Settings > APP ID).

There is a max limit of 100kb per request.

Response will be a json object, on a sucessful call you will receive response as

on failure, response will be

The MoEngage Data Import API is designed to handle high volumes of data across our customer base. We enforce API limits to ensure responsible use of the API.

Recommended rate limits of the Data Import APIs are as below -

Events - A single API request (Event / Bulk Import API) can contain one or more than one events. You should maintain a rate limit of 10000 events per minute.

Users - A single API request (User / Bulk Import API) can contain one or more than one user updates. You should maintain a rate limit of 1000 user updates per minute.

Please note that on exceeding the recommended rate limits, there is a possibility that your data processing may get delayed or your account may get blocked.

If you need to exceed the recommended limits or have any questions on the API limits, please contact your Customer Success Manager or send an email to our Support Team at support@moengage.com.

API to use - User API
This API allows you to create a new user profile (or) update profile data of existing user. It includes customer_id (Unique Identifier of User) and other User Attributes(ex: name, age etc.. ). customer_id will be used to Map Actions and Devices to User.

NOTE: customer_id is essentially the Unique Identifier which is set and passed on from MoEngage SDK as USER_ATTRIBUTE_UNIQUE_ID

customer_id in customer payload is mandatory to identify a user profile.

Signature for a user API request looks like:

To set name as John for a user with unique id john@example.com and platform android, pass the following payload

User attributes list is mentioned below:

• name (string) - name of the user
• first_name (string) - first name of the user
• last_name (string) - last name of the user
• email (string) - email of the user
• age (numeric) - age of the user
• gender (string) - "male" or "female" - case sensitive
• mobile (string) - phone number of the user
• geo (array of lat,lng in double) - location of the user for eg. [23.3,37.3]
• source (string) - acquisition source of the user
• created_time (numeric - epoch time in seconds) - user created time
• last_seen (numeric - epoch time in seconds) - user last seen time
• transactions (numeric) - no.of transactions done by the user
• revenue (numeric) - LTV of the user
• platforms (array) - platforms on which the user has interacted with the system. for eg.[{"platform":"ANDROID", "active":"true"},{"platform":"WINDOWS", "active":"true"},{"platform":"IOS", "active":"true"}]

To pass other attributes which are not part of the list, use the key value pairs that you intend to use. for ex. to set the points attribute for the user to 20

The following keywords are blocked and should not be used as attribute names - "id", "_id", ""

Mandatory fields: customer_id.

API to use - Device API
This API allows you to create a new device profile (or) update profile data of existing device. It includes customer_id (Identifier of User), device_id (Identifier of Device) and other Device Attributes(ex: model, brand, os version etc.. ).

NOTE: customer_id is essentially the Unique Identifier which is set and passed on from MoEngage SDK as USER_ATTRIBUTE_UNIQUE_ID

customer_id in device payload is mandatory to map device to user.
platform in device attributes is mandatory to run platform level campaigns.
device_id in device payload is optional and default value is customer_id value. It will be used to update specific device in future.

Signature for a device API request looks like:

We defined reserved keywords for some of Device Attributes.

To pass other attributes which aren't part of the list, use the key value pairs that you intend to use. for ex. to set the brand attribute for the device to Apple

The following keywords are blocked and should not be used as attribute names - "id", "_id", ""
Mandatory fields: customer_id, platform and push_id.

API to use - Event API
This API allows you to track actions of a user.

customer_id in event payload is mandatory to map event to user.
device_id in event payload is optional and default value is customer_id value. It will be used to map event to specific device.
platform in event payload is Not Mandatory If you do not pass platform in the event payload, we will set it as unknown on our side automatically.
Please note that you can send the platform value as Android, iOS or web based on the platform on which this event was generated.
If you are unsure about the platform on which this event happened, please send the value as unknown or do not send the value at all. Incorrect platform value will lead to inconsistencies in platform level campaigns.

Signature for event API request looks like:

Please note that we were accepting current_time and user_time earlier and the difference between user_time and current_time was used to calculate the timezone in which the even happened.

Currently, we are supporting 3 combinations - user_time and user_time_zone_offset, current_time and user_time_zone_offset and user_time and current_time to calculate the timezone of the event.

user_time_zone_offset should have a value in seconds which can be between -54000 to 54000. For example, for IST (UTC+0530), "user_time_zone_offset" will be 19800

We defined reserved keywords for Event Name and Event Attributes.

The following keywords are blocked and should not be used as event attribute names - "id", "_id", ""

Mandatory fields: customer_id and action.

API to use - Transition API
This API allows you to import “user , device and event requests” in a single batch.

Signature for transition API request looks like: