Skip to main content
POST
/
alerts
/
send
curl --request POST \ --url https://api-0{dc}.moengage.com/v1.0/alerts/send \ --header 'Authorization: Basic <encoded-value>' \ --header 'Content-Type: application/json' \ --header 'MOE-APPKEY: <api-key>' \ --data ' { "alert_id": "636b77e6e2cf83277195fb60", "alert_reference_name": "Demo_ID", "user_id": "USER_12345", "transaction_id": "TXN_ABCDEF123", "payloads": { "SMS": { "recipient": "1234567890" } } } '
{
  "message": "Successfully Received",
  "request_id": "<string>",
  "SMS": {
    "message": "<string>",
    "err_code": "<string>",
    "status_code": 123
  },
  "EMAIL": {
    "message": "<string>",
    "err_code": "<string>",
    "status_code": 123
  },
  "PUSH": {
    "message": "<string>",
    "err_code": "<string>",
    "status_code": 123
  }
}

Authorizations

​
Authorization
string
header
required

This is the authentication parameter, used for access control, must be passed along with the request.

​
MOE-APPKEY
string
header
required

This is the Workspace ID (or App ID) of your MoEngage account and needs to be passed along with the request. You can find your MoEngage APP ID in the MoEngage Dashboard API Settings.

Body

application/json

The payload containing the alert identifier, transaction details, and recipient information for each channel.

​
transaction_id
string
required

This is the unique identifier denoting the transaction for which the Alert is being sent to the user. This information is maintained by the brand and is passed in the request. The maximum length allowed for this field is 50 characters.

​
payloads
object
required

The payload contains the following channel-level information for all the configured channels.

​
alert_id
string

This field uniquely identifies the Alert to be sent to the user. For the staging endpoint, use the test alert id and for the live endpoint, use the alert id. For more information, refer to Live and Test Alerts.

​
alert_reference_name
string

This field is used to identify the Alert using your reference Name and can be used to identify the alert as an alternative to Alert ID.

​
user_id
string

This is the unique user identifier information you maintain. This information should be passed in the request to facilitate the mapping of the channel events back to the user profile to which this user_id is associated in MoEngage.

Response

Request has been received and processed. The response body contains the status for the overall request and for each individual channel.

​
message
string
Example:

"Successfully Received"

​
request_id
string
​
SMS
object
​
EMAIL
object
​
PUSH
object