Push Notifications are messages sent from the Campaign Manager tool to user's smartphones. Clients need an Android App registered to the Campaign Manager to handle the message.

Parameters on the following URL are inside braces { }

{base_url}/rest/api/tools/registerPushAndroidApp/{instanceId}/{appName}/{apiKey}/{redirectURL}/{publicKey}/{signature}

The Response XML is divided in a static part and a dynamic one, we call it dynamic because it will vary depending on the method you invoke. Please read our Response XML Basics section if you want to learn more about the response parts.

<input>registerPushAndroidApp</input>
<status>OK</status>
<description>Completed</description>
<result>
	<transactionResult> 
		<successful>true</successful>
		<message>Successful registration</message>
	</transactionResult>
</result>

Once you have your registered Android App you need to implement the device registration process. This process will connect your audience to your Push Channel once completed.

To receive Push Notifications using the Android's Platform your app must be registered to the Google Cloud Messaging.

You can complete this process completely by using this method from within your App.

Parameters on the following URL are inside braces { }

{base_url}/rest/api/tools/registerPushAndroidDevice/{instanceId}/{deviceId}/{appName}/{registrationId}/{publicKey}/{signature}

The Response XML is divided in a static part and a dynamic one, we call it dynamic because it will vary depending on the method you invoke. Please read our Response XML Basics section if you want to learn more about the response parts.

<input>registerPushAndroidDevice</input>
<status>OK</status>
<description>Completed</description>
<result>
	<transactionResult> 
		<successful>true</successful>
		<message>Successful registration</message>
	</transactionResult>
</result>

Push Notifications are messages sent from the Campaign Manager tool to user's smartphones. Clients need an iOS App registered to the Campaign Manager to handle the message.

When using iOS apps to receive Push Notifications you will need to use the Apple Push Notification System (APNs), when you do you will get a certificate that validates against Apple that is you who sending the message.

You must upload your certificate into the Campaign Manager to make it able to send your messages, please use our upload tool for this operation

Parameters on the following URL are inside braces { }

{base_url}/rest/api/tools/registerPushIosApp/{instanceId}/{appName}/{redirectURL}/{publicKey}/{signature}

The Response XML is divided in a static part and a dynamic one, we call it dynamic because it will vary depending on the method you invoke. Please read our Response XML Basics section if you want to learn more about the response parts.

<input>registerPushIosApp</input>
<status>OK</status>
<description>Completed</description>
<result>
	<transactionResult> 
		<successful>true</successful>
		<message>Successful registration</message>
	</transactionResult>
</result>

Once you have your registered iOS App you need to implement the device registration process. This process will connect your audience to your Push Channel (APNs) once completed.

You can complete this process completely by using this method from within your App.

Parameters on the following URL are inside braces { }

{base_url}/rest/api/tools/registerPushIosDevice/{instanceId}/{deviceId}/{appName}/{deviceToken}/{publicKey}/{signature}

The Response XML is divided in a static part and a dynamic one, we call it dynamic because it will vary depending on the method you invoke. Please read our Response XML Basics section if you want to learn more about the response parts.

<input>registerPushIosDevice</input>
<status>OK</status>
<description>Completed</description>
<result>
	<transactionResult> 
		<successful>true</successful>
		<message>Successful registration</message>
	</transactionResult>
</result>

You also could associate a registered device (Android, iOS) with a phone number in order to send push notifications to a device using a phone number rather than a device ID. Once the phone number is associated with a registered device, Messangi will send a SMS with a validation code to the phone number.

This is extremely useful when you need to keep it simple, because it allows you to broadcast your messages using regular mobile number lists rather than devices id list

Parameters on the following URL are inside braces { }

{base_url}/rest/api/tools/registerPushPhone/{instanceId}/{deviceId}/{appName}/{platform}/{mobileNumber}/{publicKey}/{signature}

The Response XML is divided in a static part and a dynamic one, we call it dynamic because it will vary depending on the method you invoke. Please read our Response XML Basics section if you want to learn more about the response parts.

<input>registerPushPhone</input>
<status>OK</status>
<description>Completed</description>
<result>
	<transactionResult> 
		<successful>true</successful>
		<message>Successful registration</message>
	</transactionResult>
</result>

Once the device receives the SMS with the validation code, this function allows sending the code in order to validate if the provided phone number is valid.

Parameters on the following URL are inside braces { }

{base_url}/rest/api/tools/activateRegisterPushPhone/{instanceId}/{deviceId}/{appName}/{platform}/{activationCode}/{publicKey}/{signature}

The Response XML is divided in a static part and a dynamic one, we call it dynamic because it will vary depending on the method you invoke. Please read our Response XML Basics section if you want to learn more about the response parts.

<input>activateRegisterPushPhone</input>
<status>OK</status>
<description>Completed</description>
<result>
	<transactionResult> 
		<successful>true</successful>
		<message>Successful registration</message>
	</transactionResult>
</result>