Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

A ServiceProvider may need to move a Blufi from one project to another. This API may be used to move Blufis from one ManagedProject to another ManagedProject, assuming that both projects are managed by this ServiceProvider.

This API does NOT make any configuration changes to the Blufi. If all projects are using the same WIFI Credentials, then the Blufi will be able to connect to the network and then Bluzone. If the credentials are different, then a user will need to apply the WIFI credentials via a Mobile App or SDK.

Rules for usage

  1. The API currently accepts no more than 20 Blufi id64 values at a time.

  2. The API will assign the Blufi to the first Location entity found for the target project. If this is not the desired Location, then the user will need to then login to the Bluzone Console and manually change the Location.

  3. The API will assign the Blufi to the first Blufi Template entity found for the project. This is necessary for certain UI elements to continue working and DOES NOT indicate that the associated template is the configuration used for the device.

  4. The API will skip devices that are not able to be moved, if for example, they do not belong to a ServiceProvider’s ManagedProject.

Example Request

PUT {{baseUrl}}/portal/service/{{serviceProviderId}}/_moveBlufis HTTP/1.1
Content-Type: application/json
Accept: application/json
bzspid:  {{bzspid}}

{
    "targetProjectId": 1,
    "id64s": [
        "1111",
        "2222"
    ]   
}

On success, the API will respond with a HTTP Response Code of 200 and a JSON message. Devices that are not able to be moved will listed in the messages section of the response.

Example Response

HTTP/1.1 200 OK
Connection: close
Date: Thu, 24 Jun 2021 17:18:15 GMT
Vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers, Accept-Encoding, User-Agent
Content-Type: application/json
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY
Content-Encoding: gzip

{
  "requestId": "4624555095478",
  "messages": [
    "Blufi[2222] skipped - already part of target project",
    "Moved 1 Blufis to target project[1]"
  ]
}

  • No labels