This document outlines the first steps of the integration of the Mobile Engage API.

Contents

Authentication

The Mobile Engage API is using HTTP basic authentication to authenticate the requests. The username and the password are provided by Emarsys. The username is the application code and the password is generated during the onboarding process.

HTTP communication

Mobile application developers should call Mobile Engage APIs using mobile networking best practices. For both iOS and Android, network connections should be handled asynchronously so as not to block or reduce the performance of the application or the operating system.

iOS developers may choose to use the native NSURLSession class for making HTTP requests or another HTTP client.

Android developers may choose to use Google’s preferred AsyncTask method for background network operations.

Integration

Developers may call the following endpoints from anywhere in the application:

Functions related to application lifecycle activities are maintained within the AppDelegate.m (iOS) or MainActivity.java (Android) files.