Solutions resources

An IoT developer can retrieve the data about their solutions via the Bosch IoT Things HTTP API.
However, a more convenient user interface is offered at Manage your solution.

{
  "solutionId": "string",
  "solutionSecret": "hashed string",
  "apiToken": "string",
  "serviceName": "string",
  "plan": "string",
  "status": {
      "dataVolume": "string"
  },
  "_marketplace": "string"
  "customer": {
    "name": "string",
    "email": "string",
    "info": "string"
  },
  "namespaces": {
    "namespaceId1": {
      "default": false
    },
    "namespaceIdN": {
      "default": true
    }
  }
}

Caption

  • The solutionId is generated by our service.
  • The solutionSecret is generated by our service.
  • The apiToken is generated by our service.
    Tip: The API Token is required whenever you connect to Bosch IoT Things.
  • The serviceName is “things”.
  • The plan is the service plan for your instance (e.g. Free, Starter, Standard).
  • The status - dataVolume is calculated by our service.
    In case of the Free plan you have for example a volume limit of 0.5 MB, while each managed entity (e.g. one thing) counts at least with 10 kB; for larger entities the size is counted as it effectively is.
  • The _marketplace is an internal field generated by our service.
  • The namespaces can be changed by you.
    See Manage your namespace
    Note on namespaces:
    A solution may define various namespaces. However, only one namespace is the “default” namespace. This one will be used, in case a solution creates a Thing without explicitly specifying a namespace.

The root resource itself is the endpoint for solutions.

https://<host>/api/2/solutions

The following operations are available over the HTTP API:


Note on key:
Our procedure assumes you have generated yourself a pair of public and private key.
EC - stands for the EC-DSA algorithm - is the only key type supported.
The data of the public key file (in PKCS#8 format or a X.509 certificate) will need to be Base64 encoded.

The more convenient way to manage your namespaces (in case you have booked for example a Standard plan) is to use the user interface.
See Manage your namespace.

Since Dec 2018, deletion of a namespace includes the full deletion of all entities within this namespace, such as things, policies, topology schemas and topologies. Deleting the entities will erase them from our data store without an option to restore.

In order to avoid that some authorized subject could delete all data just by trying out our interactive HTTP API documentation, the Solutions resource does not offer any longer the operations:

  • PUT /solutions/{solutionId}/namespaces
    Creates or Updates the namespaces of a Solution
  • DELETE/solutions/{solutionId}/namespaces
    Delete all namespaces of a specific Solution

However, in case you need to delete a namespace, please use the UI. The deletion of a namespace will require a second confirmation by the user. Then, it triggers the full deletion of all entities within this namespace. The progress bar displays an estimation on how long the procedure might need.

 

The more convenient way to manage your connections is to use the user interface.
See Manage your connections.

A successful registration at the solution store is part of the service booking. Find details at Book the Bosch IoT Things cloud service.

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,