POST /v1/devices/profile/actions/profile_resume
This API allows the customer to resume the suspended Verizon US eSIM profile or Global eSIM profile based on ICCID and contracted service plan. The previously suspended eSIM profile will be resumed.
Bulk operation: Supported (The callback would be one for each profile). Bulk operations have a limit of 10,000 requests.
eSIM profiles: Both Verizon US and Global.
The request header must set the content-type to JSON, contain a current ThingSpace authorization token and a current VZ-M2M session token. For more details on how to get these tokens, visit Getting Started.
Parameter Name | Data Type | Description |
---|---|---|
Authorization required |
string | HTTP Authorization bearer token: |
VZ-M2M-Token required |
string | A valid session token: |
Content-Type required |
string | Must be application/json: |
POST https://thingspace.verizon.com/api/m2m/v1//devices/profile/actions/profile_resume
Parameter | Data Type | Description |
---|---|---|
devices |
array | An array of deviceIds. Each deviceId will contain:
|
id |
string | The numeric value of the device ID type. |
kind |
string | The the type of device ID represented by the ID value. Only the following are supported by the request and both values must be present:
|
accountName required |
string | The name of the account. |
servicePlan | string | Use the Verizon ServicePlan when performing an action on the Verizon network and use the Global servicePlan when performing action for Global. |
Example request:
{
"devices": [
{
"deviceIds": [
{
"kind": "iccid",
"id": "20-digit ICCID"
}
]
}
],
"accountName": "0000123456-00001",
"servicePlan": "service plan name"
}
Status 200
A successful response shows a system generated request ID to track the request.
Example Response:
{
"requestId": "d1f08526-5443-4054-9a29-4456490ea9f8"
}
These endpoints send responses asynchronously. In order to read the results a callback is required. To learn more about callbacks, please visit About Callback Services.
Example callback response:
{
"requestId":"d1f08526-5443-4054-9a29-4456490ea9f8",
"deviceIds":[
{
"id":"32-digit EID",
"kind":"Eid"
},
{
"id":"15-digit IMEI",
"kind":"Imei"
},
{
"id":"1+ 10-digit phone number",
"kind":"msisdn"
},
{
"id":"20-digit ICCID",
"kind":"Iccid"
}
],
"deviceResponse":{
"deviceProfileResponse":{
"deviceIdentifierCollection":[
{
"id":"32-digit EID",
"kind":"Eid"
},
{
"id":"15-digit IMEI",
"kind":"Imei"
},
{
"id":"1+ 10-digit phone number",
"kind":"msisdn"
},
{
"id":"20-digit ICCID",
"kind":"Iccid"
}
],
"state":"ACTIVE",
"profileStatus":"ENABLE",
"profileRole":"LOCAL"
}
},
"status":"SUCCESS",
"callbackCount":1,
"maxCallbackThreshold":4
}
Parameter | Data Type | Description |
---|---|---|
requestId | string | The requestId being viewed. This is a system generated value from the request above. |
deviceIds |
array | An array of devices ID values associated with the ICCID being queried. Each deviceId will contain:
|
id |
string | The numeric value of the device ID. |
kind |
string | The the type of device ID represented by the ID value. This could include:
|
deviceResponse | array | Contains the deviceProfileResponse, status and number of callback records returned. |
deviceProfileResponse | array | Contains the details and status of the device and the request. |
deviceIdentifierCollection | array | Similar to deviceIds above. |
state | string | The state of the device(s) responding. |
profileStatus | string | Indicates the profile state. |
profileRole | string | This indicates if the profile is LEAD, LOCAL or DEFAULT. |
status | string | The status of the deviceResponse. |
callbackCount | string | The number of responses for deviceResponse found. |
maxCallbackThreshold | string | The maximum number of responses for deviceResponse allowed. |
All error responses will be in the following format
{
"errorCode": "The 3-digit HTML error code",
"errorMessage": "string"
}