XDK cloud connectivity

Welcome to the Bosch IoT Things service.
This is the second part of the tutorial for onboarding XDK customers.

We hope you have successfully registered your XDK in line with the guidance at the Bosch IoT Suite website for Step 1 to Step 3.

XDK tutorial
part 1

As the first and most difficult part - the device connectivity - is done by the software stack your XDK was recently flashed with, you will most probably decide for the fun part and just use the measurements reported by your XDK sensors.

API develop operate

Get familiar with our API

At this point we assume you are ready to develop your own application

  • Using the REST-like HTTP API,
  • WebSockets, or
  • Integrating with our Java client.

Our overview on Which API to use? details the benefits of each API.

note In any of these cases, please consider that the user and the application need to identify at each API request, and the Policy of the Thing (representing your XDK device) needs to allow reading for both: the application and the user.

The further examples within this tutorial will focus on the REST-like HTTP API.

Subscribe for an own Things service plan

Each API call will require an API token. In case you do not have an own Solution account yet, see How to book the service? .

Understand the Thing notation

In case you need to create an own dashboard, you will need to know the principles of the Thing notation an the details on how an XDK is structured in features.

Basically each XDK sensor will be represented as a feature.

tip Find examples on how to retrieve all features, or single values at Explore your XDK as a Thing.

Empower an App to read sensor values

In order to empower other entities to read your Thing, you will need to adjust the policy that protects your Things.
Find details at Control who may access your XDK as a Thing.

Develop your IoT App

While implementing your application, please keep in mind that the Bosch IoT Things service will require various headers (e.g. user authentication with Basic Auth, OAuth2 token, etc. as well as the API token).

Following schematic view of a user request might help you keep your application as simple as possible and use the cloud services as the “backend” for your IoT App.

sketch IoT App flow

  1. Login
    • Identify who tries to use your app.
    • You can re-direct such a request to an identity provider of your choice.
      Bosch IoT Things integrates smoothly with Bosch-ID, Bosch IoT Permissions (deprecated) and Google.
  2. Data request
    • The request specifies which data the user is interested in
  3. Response
    • The request is processed at the Bosch IoT Things service.
    • In case the user is allowed to see the data requested, this will be presented (in JSON notation)
    • In case the Thing/Feature does not exist or the user is not authorized (in the Policy) the response will report the failure with a respective description.

Professional and commercial use

For using the XDK cloud connectivity in professional and commercial scenarios do not hesitate to get in touch with us.

We would help you with changes at the XDK registration Web UI in order to register XDKs with your own Things namespace within your own Things service plan - so that you really have full control on them.

We would also offer to discuss further integration/usage options and next steps after building your first prototype towards series engineering and mass production to bring your product to life.

Please contact us via https://developer.bosch-iot-suite.com/support/.

Imprint Legal info Privacy statement