Query IMSI

purpose returns one or more imsis associated with the sim specified in the \<iccid> element traditional sims typically have a single imsi however, some sim types support multiple imsis, including multi imsi sims dual imsi configurations esim profiles with alternative imsis downloaded to the sim this request returns all imsis associated with the sim endpoint post https //api m2miportal com content type application/xml accept application/xml request (xml) \<query imsi version="1" api id="123456"> \<authentication> \<username>username\</username> \<password>password\</password> \</authentication> \<iccid>1234567890123456789\</iccid> \</query imsi> response (success) \<query imsi response api id="123456"> \<api outcome>success\</api outcome> \<imsi>234101234567890\</imsi> \<imsi>234581234567890\</imsi> \<imsi>234301234567890\</imsi> \</query imsi response> response elements element description \<imsi> one or more imsis associated with the sim maximum 15 digits per imsi if no imsis can be identified for the sim, an empty \<imsi> element will be returned behaviour notes single imsi sims will return one \<imsi> element multi imsi and esim configurations may return multiple \<imsi> elements the api does not identify which imsi is currently active or in use 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