Receiving Inbound SMS

This function returns all inbound (MO) messages for the user which have an ID larger than 'last_id'

messages_get()

GET /https://eu-api.panaceamobile.com/json?

Best practice is to use this function starting with last_id = 0, then as messages are received, to store last_id as the highest message ID you receive back from the API request. Results are limited to 50 at a time.

HTTPS GET Parameter	Value	Description
action	messages_get	This function returns all inbound (MO) messages for the user which have an ID larger than 'last_id'.
username	usernamex	Your account username.
password	passwordy	Your account password.
last_id	0	Best practice is to use this function starting with last_id = 0, then as messages are received, to store last_id as the highest message ID you receive back from the API request. Results are limited to 50 at a time.

Example:

{"status":0,"message":"OK","details":[{"id":"11","created":"2023-04-09 19:25:09","from":"27832659217","to":"20000","data":"Test MO Generated","charset":"UTF-8"},{"id":"10","created":"2023-04-09 19:24:02","from":"27832659217","to":"20000","data":"Test MO Generated","charset":"UTF-8"}]}

Reply Delivery Channels

Alternatively, you can have all replies sent to your inbox forwarded to a web service of your choice using an end-point URL to push these replies to via an HTTP GET call-back or SMPP:

In the SMS Numbers section of the dashboard, you can view and manage the various numbers associated with your account.

Here you're able to set the forwarding channel for inbound messages. Users can choose from several forwarding options: Default setting, HTTP, or SMPP, each catering to different integration and handling needs.

The Default setting refers to the Global setting for your user account meaning ALL replies that come back into your inbox. By selecting Edit you’ll be presented with a few options.

Edit Reply Delivery Channels

SMPP

SMPP (Short Message Peer to Peer) allows all inbound messages to be pushed over SMPP to your SMPP server when bound as an ESME to our platform.

Inbound Trigger

You can have multiple triggers that define different actions according to conditions/filters. Example message containing any or specific words, coming from a specific number, any or all inbound messages, etc.

Each trigger can also define one or multiple actions e.g. send an email, send an SMS, call a URL, Add/Remove a number to/from a list

HTTP

This setting will allow a server URL to be called with an HTTP GET to push all replies over HTTP. The structure of the payload when we call your URL is as follows:

http://www.yoururl.co.za/tmp/inbox/replies.php?&to=1234567890&from=27123456789&charset=UTF8&message=Hello&code=1001&client_reference=123&mcc=655&mnc=01&mo_message_id=161145956

Reply Delivery URL (HTTP)