What's new

What’s New in the Connectivity Management API

It’s Time to Plan Your Move from CDMA to 4G

On December 31, 2019, Verizon plans to retire its CDMA network (1x/EVDO, 2G/3G). These are the major dates in that plan that you need to be aware of:

  • June 30, 2018 - We will stop activating new CDMA devices.
  • July 1, 2019 - We will stop allowing the following changes for CDMA devices:
    • Device ID change
    • MDN change
    • Price plan change
    • Suspend and Resume
  • December 31, 2019 - We will shut down the CDMA network.

Now is the time to start moving your solution to our 4G network. There are multiple 4G LTE options to choose from, including Category-1 and Category-M1 choices. These industry-leading, cost-competitive, advanced-technologies enable the development of next generation solutions on the 4G LTE network. Contact your Verizon account representative for more information.

1/03/19 - release 5.9

  • The POST /devices/diagnostics/actions/list response now includes information about the device firmware version and location, for accounts that are subscribed to those ThingSpace services.
  • The number of possible profile statuses for eUICC devices has been increased to distinguish between newly downloaded profiles and those that have been downloaded and then activated or deactivated. The statuses are in the responses to POST /devices/actions/list requests.

10/03/18 - release 5.6

  • The new POST /devices/diagnostics/actions/list API method returns basic diagnostic information about a specified device, including connectivity, provisioning, and billing status.
  • Customers applying for credit approval from Verizon can now start the device activation process while waiting for the approval. The POST /devices/actions/activate method now returns an “on hold” callback while approval is pending. If credit is not approved within one week, the method returns a “canceled” callback message.
  • We have replaced a generic error message with more specific error messages for several activation-related issues.

6/28/18 - release 5.4

  • You can use POST /devices/actions/list to find devices by matching a string against the first or last part of a device identifier, in addition to the existing option to match a string against any part of a device identifier.
  • You can now set a line’s customer name and address (Primary Place of Use) in the PUT /devices/actions/goToState request. The information can be used to contact the customer, if necessary, and the zip code will be used to determine tax jurisdiction.

5/2/18 - release 5.2

New and Updated Resources

  • POST /devices/actions/list A new filter parameter 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.
  • GET /accounts/{aname}/requests/{requestID}/status Returns the processing status of a single-device asynchronous request.

3/7/18 - release 5.00

New and Updated Resources

  • GET /accounts/{aname} New request that returns information about the specified account.

2/7/18 - release 4.23

New and Updated Resources

  • An account can now register for the PromoChanges callback to receive callback messages when promotional discounts are removed from devices.
  • POST /devices/actions/list now supports pagination of large result sets and ordering devices in responses by deviceId.
  • The names of the /devices/actions/contactInfo and /devices/actions/goToState endpoints have been changed to camel case.

1/4/18 - release 4.22

New and Updated Resources:

  • Get Device Suspension Status: POST /devices/suspension/status
  • Find Mismatched Hardware: POST /devices/actions/list/imeiiccidmismatch
  • Delete Devices: POST /devices/actions/delete
  • Change Primary Place of Use with PUT /devices/costCenter

Callback Changes

ThingSpace Connectivity Management API now supports these additional callbacks:

  • Resume Tracking Notification - advises when suspended devices will auto-resume to active service
  • External Provisioning Changes - advises when service changes are made in an account through a web portal or other non-API interface
  • Device Suspension Status - asynchronous responses to POST /devices/suspension/status requests
  • Service Plan Changes - asynchronous responses to PUT /devices/actions/plan requests

Additionally, all callback messages now include requestId, status, callbackCount, and maxCallbackTreshold values. Activation and deactivation callbacks now include stateName and serviceName objects. The usageResponse object has been removed from all callbacks except those that report device usage.

12/6/17 - release 4.21

New Resources:

  • Change Device Contact Information: PUT /devices/actions/contactinfo
  • Check if Devices can be Activated: POST /devices/availability/actions/list
  • Move Devices to Another Account: PUT /devices/actions/move
  • Set Devices to Customer-Defined Service and State: PUT /devices/actions/gotostate

New Name and Address Fields

Customer name and address information now includes fields for name suffix, ZIP+4, phone, phone type, and email address.

Updated on 2/12/2016

New Resource: /devices/connections/actions/listHistory

The /devices/connections/actions/list resource has been deprecated and replaced by /devices/connections/actions/listHistory. The “listHistory” resource has the same signature as the original resource, but it will return a 202 status code if there is more data, and the response has been changed from a JSON array to key:value pairs and includes a new hasMoreData parameter.

Updated on 1/15/2016

Consistent Camel Case for URL Paths

The paths for three resources have been changed to camel case capitalization for consistency:

  • /devices/costCenter
  • /devices/actions/customFields
  • /sms/{aname}/startCallbacks

HTTP Status Code 202 and hasMoreData

Status code 202 for responses is now only used to indicate that the request was successful and there is more information to be retrieved. Those resources that can return a 202 response now also have a hasMoreData Boolean value in the response body.

These response structure for these requests was changed from a JSON array to key:value pairs to accomodate the hasMoreData parameter:

  • GET /sms/{aname}/history
  • GET /groups/{aname}/name/{gname}
  • GET /leads/{aname}

HTTP 204 Responses Replaced with 200 and success=true

These requests that used to return an empty response for success (status code 204) have been changed to return status code 200, with a response body parameter of “success”: true.

  • POST /groups
  • PUT /groups/{aname}/name/{gname}
  • DELETE /groups/{aname}/name/{gname}
  • PUT /sms/{aname}/startCallbacks