Query SIM Type

purpose returns the sim type for the sim specified in the request the sim types are as follows sim type description 1 net manx telecom (ov) single network o2 sim uk only multinet voda manx telecom (ov) multi network roaming sim using vodafone netherlands imsi, aimed at voice and data applications multinet m2m manx telecom (ov) multi network roaming sim using vodafone netherlands imsi, aimed at data only applications multinet manx manx telecom (ov) multi network roaming sim using manx telecom imsi potential use in uk data, sms and volte applications smart o2 voda manx telecom multi network dual imsi sim using o2 and vodafone netherlands imsis multinet kpn c kpn multi network roaming sim, closed user group sms multinet kpn o kpn multi network roaming sim, open user group sms multinet rog c rogers multi network roaming sim, closed user group sms o2 uk telefónica single network sim roaming on the o2 network in the uk ee ee sim single ee network in the uk with roaming options in the eu and usa 3 global hutchison ireland sim with global roaming potential aimed at higher volume data applications verizon verizon usa sim supporting lte data and sms only verizon m1 verizon usa sim supporting cat m1 data and sms only tele2 tele2 multi network roaming sim supporting data, sms and voice services including volte caburn c china telecom (hong kong) imsi multi network coverage in the asia pacific region including china caburn to telefónica (colombia) and o2 (uk) imsis telefónica provides global bootstrap coverage; o2 provides european and north american coverage including uk caburn euicc m melita (malta) telecom imsi coverage across uk, europe and north america caburn euicc mo melita (malta) and o2 (uk) imsis uk, europe and north america with additional commercial options from o2 uk imsi caburn euicc tom telefónica (colombia), o2 (uk) and melita (malta) imsis broad global bootstrap coverage with strong european and north american resilience endpoint post https //api m2miportal com content type application/xml accept application/xml request (xml) \<query sim type version="1" api id="123456"> \<authentication> \<username>username\</username> \<password>password\</password> \</authentication> \<iccid>1234567890123456789\</iccid> \</query sim type> response (success) \<query sim type response api id="123456"> \<api outcome>success\</api outcome> \<sim type>sim type\</sim type> \</query sim type response> response (failure) if a request cannot be processed, the response will include api outcome indicating failure an error description explaining the reason failure responses may occur due to invalid authentication credentials invalid or unknown identifiers (for example iccid or msisdn) invalid or missing parameters values not permitted for the specified sim type or account configuration insufficient permissions integrating systems should validate input data before submission and implement appropriate error handling and logging