De-provision devices

The API documentation for de-provisioning devices and things is provided at

https://apidocs.bosch-iot-suite.com/index.html?urls.primaryName=Bosch IoT Suite - Device Provisioning#/deprovisioning

In order to delete an entity you will need write permission for the thing.
At this point, we assume that the entities have been created via Device provisioning API. Thus, the authentication and authorization for deleting such an entity should happen for the same scope.

• Authorize with your Suite OAuth token.
  See Create a Suite Auth client.

• Click Try it out.

• Set the service-instance-id.

• Set the device-id.
  This is the same as the ID you have set at the time of provisioning it.
  Pattern is your.namespace:your-device-name.

• Additionally you will need to decide whether or not to keep other entries associated with it:
  

  • the device credentials at Bosch IoT Hub - keepCredentials - false
    (or true if you want to hinder, that a new device with the same ID will ever re-register successfully).

  • the policy at Bosch IoT Things - keepPolicy - false
    (or true if you have a policy that is used by several other things).

• Click Execute to submit the request.

Upon success, you get the status code 200, with a response body similar to the following snippet:

Delete the device credentials separately

In case you have decided to keep the credentials, but want to delete them afterwards, use Bosch IoT Hub API, and authenticate with your Suite OAuth token.

DELETE /credentials/{tenant-id}

Delete the policy separately

In case you have decided to keep the policy, but want to delete them afterwards, use Bosch IoT Things API, and authenticate with your Suite OAuth token.

DELETE /policies/{policyId}