Receiving unsubscription requests via HTTP

Overview

When a customer makes a request to unsubscribe themselves from a service (via a STOP message or a call to our automated removal service) we can inform you of this using HTTP. This page details the format of the HTTP requests which are sent to allow the processing of unsubscription by external software systems.

Contents

• Receiving unsubscription requests via HTTP
• Message format
• Response to the server
• Security considerations

Receiving unsubscription requests via HTTP

When we receive an unsubscription request from a user we can push this to you by making an HTTP GET request to a provided URL.

Message format

On receipt of an unsubscription request we will send an HTTP GET request to your server, using the parameters included in the table below:

Parameter	Description
msisdn	The MSISDN being removed
shortcode	The short code(s) to remove this MSISDN from. There will be one parameter per short code
date	Date and time of request in yyyy-MM-dd HH:mm:ss format
source	The source of the request (max length of 50 characters): IVR (call to automated removal service), STOP (MO STOP SMS sent in), UNKNOWN (other)

When sending HTTP GETs we will retry a request which fails after a timeout (currently 60 seconds). It is the customers' responsibility to filter duplicate requests - these might occur if for some reason we did not receive the HTTP response from a previous attempt within 60 secs (perhaps because the reply took longer than that or there was a network outage etc).

For example, a request to remove 447884436692 from 81111 and 82222 at 2005-08-29 19:12:45 triggered by a call to our IVR automated removal service:

http://something.customer.com/test?msisdn=447884436692&shortcode=81111&
  shortcode=82222&date=2005-08-29+19%3A12%3A45&source=IVR

Response to the server

The system expects to receive a non-empty HTTP 200 response to the request. If a 200 response is not given within a timeout (currently 60 seconds) then the request will be retried.

Security considerations

To ensure the authenticity of the HTTP requests you should only accept requests from the following MX Telecom IP addresses:

• 83.166.68.0/23 (ie 68.0 -> 69.255)

The HTTP endpoint can be an HTTPS (SSL) URL to protect the data whilst in transit.

About MX Telecom MX Telecom is a leader in wireless technology. MX Telecom offers an easily accessible gateway to data, voice and video messaging services including 2-way and premium SMS, multimedia messaging, interactive voice response, location-based services, video short codes, Internet and TV related solutions. For more information, MX Telecom can be reached on 0845 666 7778, or via email at sales@mxtelecom.com.