API Reference

QuerySimResources

With this operation, it is possible to retrieve information about one or multiple SIM resources by entering a valid IMSI, MSISDN, IMEI, ICC, or customer label, and optionally, a range.

IMPORTANT! This SOAP API has a REST replacement which we strongly suggest as alternative.
Please use this REST API instead: 

IoT Accelerator REST API

Look at the API migration tutorial Here

The WSDL is available at the following URL, where the <baseURI> parameter is provided by the operator:

— <baseURI>/dcpapi/SubscriptionManagement?WSDL

EXAMPLE OF API REQUEST:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" ⇒
xmlns:sim="http://api.dcp.ericsson.net/SubscriptionManagement">
<soapenv:Header/>
<soapenv:Body>
<sim:QuerySimResources>
<resource>
<id>123456789123456</id>
<type>imsi</type>
</resource>
<range>2</range>
</sim:QuerySimResources>
</soapenv:Body>
</soapenv:Envelope>
EXAMPLE OF API RESPONSE:
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<ns2:QuerySimResourcesResponse
xmlns:ns2="http://api.dcp.ericsson.net/SubscriptionManagement">
<simResource>
<customerLabel>Operator A SIM 000</customerLabel>
<msisdn>1234567891234</msisdn>
<imsi>123456789123456</imsi>
<icc>123456789123</icc>
<pin1>0000</pin1>
<pin2>1111</pin2>
<puk1>00000000</puk1>
<puk2>11111111</puk2>
<imei>123456789123</imei>
<customerNo>00000001</customerNo>
<site></site>
<accessControlClass></accessControlClass>
<roamProfileName>Operator A RP 2</roamProfileName>
<roamProfileDesc>Operator A Roaming Profile 2</roamProfileDesc>
<deviceTerminalType>123456789123</deviceTerminalType>
<simSubscriptionStatus>Ordered</simSubscriptionStatus>
<simResourceStatus>Ordered</simResourceStatus>
<simCardDescription>Operator A SIM Card2_9</simCardDescription>
<productOfferName>Operator A PO 2</productOfferName>
<deliveryDate>2013-12-18T16:54:23.000+01:00</deliveryDate>
<firstActivationDate>2013-12-18T16:54:23.000+01:00</firstActivationDate>
</simResource>
</ns2:QuerySimResourcesResponse>
</env:Body>
</env:Envelope>