Standard APIsConnectivity ManagementAPI EndpointsEmbedded SIM Including Consumer eSIMActivate Device Through Profile

API Reference

Activate Enable a Device (for eUICC)

Uses and Requirements

Enable a eUICC device, or multiple devices, for a profile. Enabling a device brings the device under the control of a profile.

Request Components

HTTP Request:

POST https://thingspace.verizon.com/api/m2m/v1/devices/profile/actions/activate_enable

Header Parameters

The request header must contain a current ThingSpace authorization bearer token and a valid VZ-M2M session token, and must set the content-type to JSON.

Parameter NameData TypeDescription
Authorization requiredstringHTTP Authorization bearer token.
VZ-M2M-Token requiredstringA valid session token returned by POST /session/login.
Content-Type requiredstringMust be application/json.

Request Parameters

ParameterData TypeDescription
devices requiredarrayAn array of deviceIds. Each deviceId will contain: id kind
idstringThe numeric ID of the device.
kindstringThe the type of device ID represented by the ID value. This could be: imei iccid mdn eid
accountName requiredstringThe name of the account.
servicePlanstringThe name of the service plan controlling billing for the account.
mdnZipCodestringThe 5-digit zip code of the profile

Request Body

{
   "devices":[
      {
         "deviceIds":[
            {
               "id":"15-digit IMEI",
               "kind":"imei"
            },
            {
               "id":"32-digit EID",
               "kind":"eid"
            }
         ]
      }
   ],
   "accountName":"0000123456-00001",
   "servicePlan":"name of the service plan",
   "mdnZipCode":"5 digit zip code"
}

Success Responses

A successful response shows a system generated request ID to track the request.

Example Success Response:

{
  "requestId": "595f5c44-c31c-4552-8670-020a1545a84d"
}

Callback Response Parameters

These endpoints send responses asynchronously. In order to read the results a callback is required.To learn more about callback, please visti About Callback Services.

Example callback response:

{
   "username":"username",
   "password":"password",
   "requestId":"d1f08526-5443-4054-9a29-4456490ea9f8",
   "deviceIds":[
      {
         "id":"20-digit ICCID",
         "kind":"iccid"
      },
      {
         "id":"15-digit IMEI",
         "kind":"imei"
      },
      {
         "id":"32-digit EID",
         "kind":"eid"
      },
      {
         "id":"10-digit MDN",
         "kind":"mdn"
      }
   ],
   "deviceResponse":{
      "deviceProfileResponse":{
         "deviceIdentifierCollection":[
            {
               "id":"20-digit ICCID",
               "kind":"iccid"
            },
            {
               "id":"15-digit IMEI",
               "kind":"imei"
            },
            {
               "id":"32-digit EID",
               "kind":"eid"
            },
            {
               "id":"10-digit MDN",
               "kind":"mdn"
            }
         ],
         "state":"Active",
         "profileStatus":"ENABLE",
         "euiccStatus":"EXECUTED_SUCCESS",
         "euiccStatusCode":"1.2.365",
         "euiccStatusDesc":"EUICC device profile has been updated",
         "euiccSubAddressUpdateStatus":"EXECUTED_SUCCESS",
         "euiccSubAddressUpdateStatusCode":"1",
         "euiccSubAddressUpdateStatusDesc":"SUCCESS: Address has been updated",
         "carrierName":"VerizonWireless",
         "profileRole":"LEAD"
      }
   },
   "status":"SUCCESS",
   "callbackCount":1,
   "maxCallbackThreshold":4
}

Callback Parameters

ParameterData TypeDescription
usernamestringThe username making the request.
passwordstringThe password associated with the username.
requestIdstringThe requestId being viewed. This is a system generated value from the request above.
deviceIdsarrayAn array of devices being queried by the request. Each deviceId will contain: id kind
idstringThe numeric ID of the device.
kindstringThe the type of device ID represented by the ID value. This could be: imei iccid mdn eid
deviceResponsearrayContains the deviceProfileResponse, status and number of callback records returned.
deviceProfileResponsearrayContains the details and status of the devices and the request.
deviceIdentifierCollectionarraySimilar to deviceIds above, but this lists the devices responding.
statestringThe state of the device(s) responding.
smsrOidstringSystem Management Service Request Object ID. This is a system generated ID to track transaction requests made by the device.
profileStatusstringIndicates the profile state and will show what request was made.
euiccStatusstringThis shows how the device, or devices, has responded to the request. eUICC is embedded universal integrated circuit card and refers to the SIM card for the device. For more information, visit Working with eUICC Devices.
euiccStatusCodestringThe system generated status code for an eUICC device.
euiccStatusDescstringDescription of the eUICC status code
euiccSubAddressUpdateStatusstringStatus of any address update requests.
euiccSubAddressUpdateStatusCodestringA system generated status code for an address update request.
euiccSubAddressUpdateStatusDescstringA description of the status code from above.
statusstringThe status of the deviceResponse.
callbackCountstringThe number of responses for deviceResponse found.
maxCallbackThresholdstringThe maximum number of responses for deviceResponse allowed.

Failure Responses

All error responses will be in the following format

{
  "errorCode": "The 3-digit HTML error code",
  "errorMessage": "string"
}

On this page