IMIconnect Developer Hub

Welcome to the IMIconnect Developer Hub. You'll find all the resources to help you get started with IMIconnect quickly. We are here to support you if you get stuck. Let's jump right in!

Get Started

Create a Mobile App on IMIconnect

In order to use Push notification and in-app messaging features, you first need to create an app on IMIconnect platform. This app holds information like, the FCM API key corresponding to your mobile app. In return you get an APP ID and a client key, which need to be embedded in your mobile app in order to link it to the app created on IMIconnect.

Further to send push notifications or in-app messages, you need to map this app asset to a service.


Your account administrator should have been provided a url to the IMIconnect Portal, this url is unique to your account. If you do not have your account url, please contact your account administrator.


  1. Login to your IMIconnect Portal account using your unique account url.
  2. From menu bar, go to Assets, and click on Apps as shown below.
  1. In the app configuration screen, set a name to your app and make a note of 'CLIENT KEY' provided in the section below that.
  1. Next, click on 'CONFIGURE' as shown in image to configure OS specific Push Notification settings.

Android Push Notification Configuration

  1. In the pop-up that appears, provide the FCM Server key corresponding to your Firebase project. In the second image below, you can see the section from where you can access the FCM server key from the firebase console.
    Copy the code snippet provided in the 'PERMISSIONS' section and paste it in your manifext.xml file.
Get your FCM server key

Get your FCM server key

iOS Push Notification Configuration

  1. In the pop-up that appears, if you want to use APNS as the Push Notification gateway, provide the Certificate Password, select the gateway type of your APNS project and provide the certificate file to complete your configuration process. Alternatively you can use FCM as gateway.

Configuration for In-App Messaging

  1. Enable In-App messaging and select the primary and secondary connection protocol from the selectlist


Two transport protocols are available for establishing an In-App Messaging connection with IMIconnect (Web Socket and MQTT). You can configure them as primary and secondary. If a connection fails to established on the primary protocol, it will fall back to the secondary protocol

  1. For an end-to-end encrypted messaging service, you must select both the check-boxes (Use Secured Port and Enable Payload Encryption) show in the image

Configuration for Device Monitoring

  1. To monitor device attributes, like IMEI No., Geo-Location etc, enable Device Attributes and click on 'CONFIGURE' as show below.
  1. In the pop-up that appears, select the device attributes you wish to monitor.
  2. Next, define the monitoring frequency by selecting an interval from the select-list available.
  3. Now copy the code snippet available in the 'PERMISSIONS' section and paste it in your manifest.xml file in case of Android or plist file in case of iOS.
Device Attribute configuration for iOS

Device Attribute configuration for iOS

Device Attribute configuration for Android

Device Attribute configuration for Android

  1. If you want to authorize all communications over in-app messaging, you can do so by enabling JWT Authorization. Once enabled, you'll need to provide the JWT secret key that will be used for validation.
  1. Finally, click on SAVE to complete your app asset creation process and hit the back button, to land on the apps page. You can now see your app listed with an App-ID.

You'll have to embed this APP ID in your app code. You can learn more about it in Quickstart guides available in each SDK documentation.

You have now successfully created a mobile app asset on IMIconnect

What's Next

Build your first mobile app.

Android Quickstart Guide

Create a Mobile App on IMIconnect

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.