Overview

HLR lookup API exposes the ability for Merchants to provide a msisdn and get network information returned. Additionally the API can be used to pass a User on Data and get network and msisdn information returned so the merchant can provide customised flows depending on the users network.

There are three endpoints. One for passing in MSISDN for WIFI lookup (JS) and one for data carriers (JS) and one for server side POST API calls

JS:Carrier: http://pfi.imimobile.net/msisdnlookup/ajax/carrier
JS: WIFI: http://pfi.imimobile.net/msisdnlookup/ajax/lookup
S2S: http://pfi.imimobile.net/msisdnlookup/web/lookup

Both API’s can be interacted with using standard POST method
JS can be done using datatype jsonp.

JS examples

Carrier Lookup

<script type="text/javascript"> $.ajax({ url: "http://pfi.imimobile.net/msisdnlookup/ajax/carrier", type: "POST", dataType: "jsonp", data: { merchantToken: 'xxxxxxxxxxxxxxxxxxxxxxx', sessionToken: 'xxxxxxxxxxxxxxxxxxxxxxx' } }).done(function(result) { document.write(result); }).fail(function() { document.write('it failed'); }); </script>

WIFI Lookup

<script type="text/javascript"> $.ajax({ url: "http://pfi.imimobile.net/msisdnlookup/ajax/lookup", type: "POST", dataType: "jsonp", data: { merchantToken: 'xxxxxxxxxxxxxxxxxxxxxxx', sessionToken: 'xxxxxxxxxxxxxxxxxxxxxxx', msisdn: 'xxxxxxxxxxxxxxxxxxxxxxx' } }).done(function(result) { document.write(result); }).fail(function() { document.write('it failed'); }); </script>
Body Params
string

Merchant token as provided to you for verification

string

Session token (must be unique per user)

int32

the msisdn of the user you wish to lookup in format example: 447768240408

Responses

Language
Choose an example:
application/json