Receive Mobile App Users' Responses over API

Infobip supports receiving incoming push notifications from mobile app users. When it comes to receiving incoming messages, you can choose between two basic methods:

• HTTP forward method - Allows you to receive incoming messages from your mobile app users in real time.
• Pull method - Allows you to fetch new messages from the Infobip server over API whenever you want.

Before you can start receiving messages, you need to configure the application for incoming messages. You can find instructions on how to set up each scenario in the Configuration section below. It’s up to you to decide which method to use, depending on your use case.

HTTP Forward Method

Use this method to receive incoming messages in real time. Every message received from a mobile app user will be forwarded to an arbitrary URL provided in the Action Setup. The arbitrary URL should be able to receive POST requests.

Pull Method

All messages received from your mobile app users will be received on the Infobip platform and will be there until you decide to access them over API call (opens in a new tab) which will return the received messages.

Configuration

The Configuration is a logical container for actions. You can choose a method of incoming message delivery through the Action setup, but before you do that, you must create the configuration.

List All Configurations

Each application within the Infobip platform is uniquely identified with the APPLICATION CODE.

Use the list all configurations (opens in a new tab) method to get all configurations of your application. If successful, you will receive a list of configurationKeys.

Get Single Configuration

Use the APPLICATION CODE and Configuration Key to get single configuration (opens in a new tab).

Path parameters

Create New Configuration

Each application within the Infobip platform is uniquely identified with the APPLICATION CODE. Use this method (opens in a new tab) to create a new configuration within the application. If successful, you will receive a configurationKey. Attempting to create a new configuration when another configuration already exists will result in the 409 CONFLICT status.

Delete configuration

To delete the configuration, use this method (opens in a new tab) with the configurationKey (opens in a new tab) you want to delete and APPLICATION CODE you want to delete the configuration from.

Path parameters

Setup Action

Action Models

Different actions have different models depending on the logic that the action triggers. These models are used as a request and response bodies for GET and POST methods.

HTTP FORWARD Action

Pull Action

List All Actions

Use the list all actions (opens in a new tab) method to return actions for a given application configuration, if any. If successful, response will contain all actions for the given configuration.

Create New Action

To create a new action for configuration within application use the create a new action (opens in a new tab) method.

Path parameters

Request example

HTTP FORWARD

 
    {
    
        "type": "HTTP_FORWARD",
    
        "forwardUrl": "https://www.myDomain.com/messageReceiver",
    
        "callbackData": "callbackData"
    
    } 
 

Request example

Pull

 
    {
        "type": "PULL",
        "callbackData": "callbackData"
    }
 

Delete Action

To delete an action use the delete (opens in a new tab) method.

Path parameters