Release Notes Archive

The new SetUsageSegmentationLabels API method allows you to access your owned usage segment that is operated on devices owned by another customer. This new method is part of the Carrier Service.

WSDL updated to include GetSubscriptionInformation method.

The UploadActivate method has been enhanced to set IP Address on devices that are submitted for uploading to DMD and then subsequently activated.

The new CheckOrderStatus API method allows you to check the status of a provisioning order. Initially, only activations are supported. This new method is part of the Device Service.

The new GetSubscriptionInformation API method allows you to get SIM Secure subscription information such as the types of licenses and quantities purchased, the number of licenses assigned and how many are available. This new method is part of the Account Service.

The new UploadActivate API method allows you to submit up to 10,000 devices for upload to the Verizon Device Management Database (DMD). Once the devices are successfully uploaded, they will be automatically submitted for activation. This new method is part of the Device Service.

The new UploadDevices API method allows you to submit up to 10,000 devices for upload to the Verizon Device Management Database (DMD). This new method is part of the Device Service.

You can now set a line's customer name and address (Primary Place of Use) in the GoToState API method. The information can be used to contact the customer, if necessary, and the zip code will be used to determine tax jurisdiction.

The StateService WSDL has been updated for this change.

A new filter in the GetDeviceList API method lets you search for devices by only providing part of a device identifier. For example, you could provide the last four characters of an ICCID instead of the entire ICCID. All devices that contain the provided string in their ICCIDs would be included in the response.

The DeviceService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

The GetRequestStatus API method returns the current status of the processing of an asynchronous request, either Pending, Succes, or Failed.

The AccountService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

A new DeleteDevices API method lets you remove deactivated devices from an account. Devices are removed immediately. You can use this method instead of contacting Verizon Customer Support to request device removal.

The DeviceService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

Account names and numbers are the same for most accounts, in the format ##########-##### (10 digits, a hyphen, then five more digits). Some accounts have different names, though, and you can use the new GetAccountInformation API to find out. You can provide either an account name or an account number in the request, and the response will contain both the name and number for the account.

The AccountService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

The GetDevicesInformation API accepts a list of devices and either an account name or number, and returns a validation of whether each device is in the account, plus a subset of information about each device. You can use this API to verify account ownership of devices before sending other API requests that would return errors if devices are not in a specified account.

The DeviceService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

Original equipment manufacturers (OEMs) upload device information to Verizon, and for some devices that includes the ID of the device that a particular SIM card is expected to be installed in. SIMs may be moved between devices, though, so the expected pairing doesn't always occur, or may change once the SIM is in use. The new GetImeiMismatch API checks a provided list of devices to see if the SIMs were activated in different device during a specified time frame.

The DeviceService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

The GetDeviceUsageHistory response and the GetAggregateDeviceUsage callback now show separate totals for the number of SMS messages sent to devices (mobile terminated, or MT) and received from devices (mobile originated, or MO), as well as the total number of SMS messages during a reporting period.

There are no WSDL or schema updates required for this change, so the SDK has not been updated.

The GetDeviceInformation and GetDeviceList responses now include a new RoamingCountry extended attribute that contains the name of a country if RoamingStatus = Roaming, or empty if NotRoaming.

There are no WSDL or schema updates required for this change, so the SDK has not been updated.

The new CheckDeviceAvailability API enables you to verify that your devices are ready for new service before you request activations. The API checks that devices are certified for the Verizon Wireless Network, registered with Verizon by the manufacturer, and not already active with a mobile terminal number (MTN).

The asynchronous response is sent by a new DeviceService callback service.

The DeviceService WSDL has been updated for this change, and there is a new callback in the callback schema. UWS Explorer has also been updated to include the new functionality.

All callbacks now include CallbackCount and MaxCallbackThreshold parameters to provide information about callback retries for unsuccessful callbacks.

• CallbackCount respresents the number of times the ThingSpace Platform has attempted to send the current callback. The first attempt will have a value of 1. If the callback fails (that is, the receiving system does not acknowledge receiving it), the ThingSpace Platform will try again in 5 minutes and the value will be incremented to 2. This will continue until the MaxCallbackThreshold value has been reached, and the callback will not be sent again after that.
• MaxCallbackThreshold is the number of times that the ThingSpace Platform will attempt to send a callback. It has a fixed value of 4.

There are no WSDL or schema updates required for this change, so the SDK has not been updated. The 4.7 SDK (October 2016) is still the most current version.

The customer name is now returned as an Extended Attribute in the response to a GetLeadInformation request.

There are no WSDL or schema updates required for this change.

Unacknowledged callback messages will be retried 3 times at 5 minute intervals, for a total of 4 attempts to send the message.

Failed callback messages will be archived for 30 days. During the 30 day period, customers can contact support with the Request ID of failed callbacks and ask for them to be resent.

The IMEI and SKU associated with a SIM can change when a device completes the Over-The-Air (OTA) Activation procedure. To help customers track these changes:

• The ThingSpace Platform will send an ExternalProvisioningChanges callback when a device completes OTA activation.
• The callback contains the values of the IMEI and SKU prior to OTA Activation, and the timestamp of the most recent OTA Activation.
• The GetDeviceInformation and GetDeviceList APIs return new extended attributes containing the IMEI and SKU prior to OTA Activation and the timestamp of the most recent OTA Activation.

Beginning December 1, 2015, Verizon will begin deleting historical records from the ThingSpace Platform database in keeping with the data retention policy outlined below. This action will limit the amount of historical data that you can access using the Wireless Network Services APIs.

System Logs The information contained in the Master Log, Transaction History Report and Notification Log will be kept for 12 months. Log data that is older than 12 months will be deleted.

Usage Reports The information contained in the Device Usage Report, Aggregated Usage Report and Rated Usage Report will be kept for 12 months. Log data that is older than 12 months will be deleted.

Connection Reports The information contained in the Connection History Report and Connected Session History Report will be kept for 3 months. Log data that is older than 3 months will be deleted.

If you want to retain historical data before it is deleted, please use the appropriate API to retrieve the data from the ThingSpace Platform and store it on your local resources.

Cost center codes can be set when devices are activated, and can be updated or removed at any time.

• The ChangeDeviceState-Activate API has been enhanced to allow assigning a cost center code when activating devices. All devices in an activation request will use the same cost center code value, if specified.
• A new ChangeDeviceCostCenter API allows changing or removing a cost center code from one or more devices.
• The GetDeviceInformation and GetDeviceList APIs have been enhanced to return the cost center code as an extended attribute.

4G devices with embedded SIMs can be activated by providing the SIM ICCID and a SKU that identifies the device type.

• The ChangeDeviceState-Activate API can accept a SKU and ICCIDs in an activation request, in lieu of IMEI and ICCID pairs. All devices in an activation request will use the same SKU value, if specified.
• The GetDeviceInformation and GetDeviceList APIs have been enhanced to return the SKU as an extended attribute.