You can use this API to store any communication sent to customers for later access.
{X} in the Base URL with your specific Data Center number. Check the mapping page to find yours.The API request is authenticated through Basic Authentication (Base64-encoded username:password).
How to obtain credentials:
Header format: {"Authorization":"Basic Base64_ENCODED_APPKEY_APIKEY=="}
This is the Workspace ID (earlier APP ID) of your MoEngage workspace. Found in Settings -> Account -> APIs -> Workspace ID.
The request body contains the parameters required to identify and retrieve the message.
This field denotes the unique identifier of the user.
This field denotes the delivery type of the channel.
ONE_TIME, PERIODIC, EVENT_TRIGGERED, LOCATION_TRIGGERED, DEVICE_TRIGGERED, API_TRIGGERED, BUSINESS_EVENT_TRIGGERED This field denotes the campaign type.
Supported Values:
General Push Campaign, Autotrigger Campaign, Geo-fencing Campaign, Business Event Trigger Push Campaign, sms, Business Event Trigger SMS Campaign, Email Campaign, Email Triggers, Business Event Trigger Email Campaign, Inform Email, Inform SMS, Inform Push The campaign channel.
EMAIL, SMS, PUSH, FLOWS The sent time of the campaign as a Unix epoch timestamp.
1716972486
This field denotes the campaign ID.
The name of the event (e.g., 'Email Sent', 'SMS Sent', 'Notification Sent iOS').
Email Sent, SMS Sent, Notification Sent iOS, Notification Received Android, Notification Received Web The target platform of the campaign.
IOS, ANDROID, WEB, EMAIL, SMS, MWEB The event ID. Required for event-triggered campaigns.
moe_event_id if any event attribute is present for campaigns.moe_transaction_id for alerts.The rate limit for this endpoint is 1000 RPM.