API Reference

Move Devices to Another AccountCopy Anchor Link

Uses and RequirementsCopy Anchor Link

Device Moves vs. Transfers

A Device Move involves moving a device from one billing account to another billing account (e.g. 0123456789-00001 to 9876543210-00001). A Device Transfer involves moving a device from one sub-account to another sub-account under the same billing account (e.g. 0123456789-00001 to 0123456789-00002). Device History

All device history (usage history, connection history, etc.) from before the move is retained under the original billing account. Data usage and connections that occur after the move are tracked under the new account. Device attributes, such as service plan and custom field values, are retained when possible, or new values can be specified. Usage Notes

• You can only move devices that are in the active state.
• The suspension history for moved devices is reset to zero days suspended.
• Use separate requests to move 3G and 4G devices unless your accounts are set up to allow both types of devices in the same service plan.
• Only move devices from one account at a time. If the request includes devices from more than one account, the devices from one account will be moved and the devices from other accounts will fail.
• Both accounts that are "move from/move to" must be under the same ECPD
• You must have account access to both the "move to" account and the "move from" account

Account Requirements

• The customer profile must be enabled for IoT Order flow.
• Devices cannot be moved between subaccounts under a single billing account.
• The billing accounts cannot have customer-defined stage states.

ThingSpace sends an asynchronous CarrierService callback message for each device in the request when the device has been moved, or if there was a problem and the move failed.

Request ComponentsCopy Anchor Link

HTTP Request

PUT https://thingspace.verizon.com/api/m2m/v1/devices/actions/move

Resource Path and Query Parameters

None.

Header ParametersCopy Anchor Link

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.

equest BodyCopy Anchor Link

The request body identifies the devices that you want to move to another account. You can either specify individual devices in the devices parameter, or you can use the filter parameters to work with devices that match the filter parameter values.

Example Request Body

Move a single device

{
  "devices":[
    {
      "deviceIds":[
        {
          "kind":"ESN",
          "id":"19110173057"
        }
      ]
    }
  ],
  "accountName":"0212345678-00001",
  "servicePlan":"M2M5GB"
}

Move all devices that are in a specified device group and that have a specified custom field value

{
  "filter":{  
    "groupName":"Short-Haul Trucks",
    "customFields":[  
      {  
        "key":"CustomField1",
        "value":"East Region Trucks"
      }
    ]
  },
  "accountName":"0212345678-00001",
  "servicePlan":"M2M5GB"
}

Success ResponsesCopy Anchor Link

Status 200

Example Success ResponseCopy Anchor Link

{
  "requestId": "ec682a8b-e288-4806-934d-24e7a59ed889"
}

Example Success Callback ResponseCopy Anchor Link

{
  "username":"",
  "password":"",
  "requestId":"ec682a8b-e288-4806-934d-24e7a59ed889",
  "deviceIds":[
    {
      "id":"19110173057",
      "kind":"Esn"
    }
  ],
  "deviceResponse":{
    "usageResponse":[ ],
    "moveDeviceResponse":{
      "deviceIds":[
        {
          "id":"19110173057",
          "kind":"Esn"
        }
      ],
      "accountName":"0212345678-00001"
    }
  },
  "status":"Success",
  "callbackCount":1,
  "maxCallbackThreshold":4
}