Welcome to Bosch IoT Rollouts.

This guide is intended to give a quick overview of the most prominent workflows of Bosch IoT Rollouts.

This documentation is dedicated to Bosch IoT Rollouts as a standalone service.

If you are using the Bosch IoT Rollouts functionalities as part of your Bosch IoT Device Management subscription, please read the relevant documentation here.

This is important, as some functionalities and workflows may differ.

The following sections will guide you step by step:

The workflows build upon one another, so it is possible to go through them successively. However, they can also be used for reference later on by heading directly to the section of interest.

Let’s start at Subscribe a Bosch IoT Rollouts instance.

API Replacement Token

The given code snippets use replacement tokens, to indicate which information has to be provided by the user. The following table describes where to find the respective token.

Token	Description
HOST	see Service plans and regions
TENANT_ID	see Binding Credentials¹
USERNAME	see Binding Credentials¹
PASSWORD	see Binding Credentials¹
TARGET_TOKEN	see Target security token authentication to enable the feature. A device’s security token is found in the Target Details table in the Deployment view:
GATEWAY_TOKEN	see Gateway security token authentication to enable the feature

¹Binding Credentials
With your subscription you have received Binding Credentials (e.g. in bosch-iot-suite.com > my account > subscriptions).
This JSON style document contains your Tenant ID among others.

Device Management Federation API

The guide does not contain examples for the Device Management Federation API (DMF). Its protocol flow is described in the respective section of the API guide.

Moreover, the hawkBit Device Simulator implements a DMF client, which can be used as a reference implementation.