Reassign device organization

Reassign device(s) to a different organization. Only devices which hardware is controlled by the partner can be reassigned

POST /api/partner/reassignDeviceOrg

Reassign device organization

cURL

curl --request POST \
  --url https://api2.rhombussystems.com/api/partner/reassignDeviceOrg \
  --header 'Content-Type: application/json' \
  --header 'x-auth-apikey: <api-key>' \
  --header 'x-auth-scheme: <x-auth-scheme>' \
  --data '
{
  "sourceOrgUuid": "AAAAAAAAAAAAAAAAAAAAAA",
  "targetOrgUuid": "AAAAAAAAAAAAAAAAAAAAAA"
}
'

200

{
  "statuses": {}
}

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

Request object for reassigning devices from one organization to another.

sourceOrgUuid · string<RUUID> | null · required

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

targetOrgUuid · string<RUUID> | null · required

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

serialNumbers · (string | null)[] | null

Serial numbers of the devices that should be reassigned to target organization

Serial numbers of the devices that should be reassigned to target organization

Response

200 - application/json

OK

Response object containing the status of device reassignment operations.

statuses · object

Map of device serial numbers to their reassignment operation status

Show child attributes