Skip to main content
POST
Move controlled hardware to another managed client

Authorizations

x-auth-apikey
string
header
required

Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).

Headers

x-auth-scheme
enum<string>
default:partner-api-token
required

Authentication scheme identifier. Use api-token for standard API key authentication, partner-api-token for partner API key authentication. Must be paired with the x-auth-apikey header containing your API key.

Available options:
api-token,
api,
partner-api-token,
partner-api

Body

application/json

Move controlled devices from one managed client to another.

fromClientOrgUuid
string<RUUID> | null
RUUID

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

moveLicense
boolean | null

When true, an MSP-owned device license follows the device to the target org.

serials
(string | null)[] | null
toClientOrgUuid
string<RUUID> | null
RUUID

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

Response

200 - application/json

OK

Per-serial outcome of a hardware move.

blocked
object[] | null
error
boolean | null
errorMsg
string | null
failed
object[] | null
moved
(string | null)[] | null
warningMsg
string | null
Last modified on September 22, 2026