In order to use the HTTP/HTTPS based API, you will need to have a system that has internet connectivity on outbound port 80 (HTTP) or 443 (HTTPS). This connectivity may be direct to the internet, or may be via a firewall or proxy server.
Additionally, should you wish to receive delivery reports (DLRs) from the mGage system, you must have a web server that is able to receive incoming requests from the Internet on either port 80 (HTTP) or 443 (HTTPS). This web server does not necessarily have to be running on the same machine that is sending messages to mGage.
This is one of the simpler server-based forms of communication. It can be used either in the form of a HTTP POST or HTTP GET. We recommend POST for larger data transfer and data security. All calls to the API must be URL-encoded. The parameter names are case sensitive.
For each successful submission, the API would return a unique message ID (MID) for that transaction. The Client’s Application should capture the MID and if a Delivery Report (DLR) can be fetched against that MID. This message ID then can be used to track the status of the message and receive the DLR against this MID through DLR URL
