Overview
Search…
⌃K

Request a Token Today

Request your first token through our demo API today. We have registered two demo devices that can be used with our publicly available Postman collection to give you an impression of our solution.
Feel free to reach out to us if you would like to engage in a pilot project and register your own devices in our demo environment.

Getting Started

Get started today by clicking on the button below to get our Postman collection that can be used to simulate an IoT device requesting a token and accessing our demo IoT platform.
Run in Postman

Requirements

To use our Postman collection you will require a Postman account that can be created for free.

Setup Postman

If you are unfamiliar with Postman please follow these steps to set up our Postman collection and environment.

1. Get our collection

Click on the "Run in Postman" button at the top of this page. You will be asked to fork our Postman collection and environment. Click on the "Fork Collection" button.

2. Fork collection

Next, you might be asked to log in first. Once logged in you will be asked to give the collection a label and select your Postman workspace where you want our collection to be set up. Make sure that the check box for "Watch original collection" is checked, to get notified in case we update anything in our Postman collection. Click on the "Fork Collection" button.

3. Verify setup

Make sure that our Postman collection and environment have been successfully imported. You can verify this by checking the "Collections" and "Environment" tabs on the left-hand side.

Use Postman

Now that you have set up Postman you are ready to request your first token
🎉
Start by opening our "Demo" collection and make sure that you have selected our Postman "Demo - Environment" in the environment selector in the top right corner.

Request a token

To request a token open the "Token" request in our "Demo" collection. To simulate an IoT device Postman will execute the "Pre-request Script" that generates the JWT that is required to authenticate to the IoT identity provider. You will find the generated JWT in the environment variable called "jwtBearer" if you wish to review it after you have sent the request.
Click on the "Send" button to send the request to our IoT identity provider. If the request was successful you will see the issued access token as displayed in the screenshot below.
Congratulation, you just have successfully requested your first access token
🥳

Inspect your token

Now, let's inspect your shiny new token to see what the seemingly random string actually means. To inspect and validate the access token you need to send it to the introspection endpoint of our IoT identity provider. Open the "Introspect" request in our "Demo" collection. The access token is automatically persisted in the environment variable called "access_token" which is now used as a parameter in the body of the introspection request.
Click on the "Send" button to send the request to our IoT identity provider. If the request was successful and the token is still valid you will get a response that contains the different claims of the access token.
In case the access token is no longer valid the IoT identity provider will simply replay with
{
"active": false
}

Use your token

Now it is time to put your token to work. Use the token to access our demo IoT platform and upload some random data. The IoT platform will validate the access token using the introspection endpoint of our IoT identity provider. The validation includes a check if the access token is still valid and has the right scope to access the temperature resource. Open the "IoT Platform - Temperature Resource" request in our "Demo" collection. Postman will insert the latest access token and generate a random value automatically.
Click on the "Send" button to send the request to our demo IoT platform. If the request was successful the IoT platform will echo the random value that was uploaded along with the device ID that was found in the access token used to authenticate the request.
Congratulation, you just have securely uploaded data to our demo IoT platform
🥳

Authentication Challenge

Now that you had your first experience with using our IoT identity provider let's make it a bit more interesting
😉
As you may already have noticed, the request to the humidity resource of the demo IoT platform is failing with a 403 response. Make it succeed!
All information you need for this challenge is available in the Demo infrastructure section.

Additional Details

Demo infrastructure

Please use the following table to identify all available components of our demo environment.

OAuth clients

OAuth Client ID
Allowed Scopes
demo-temp-sensor-client
temp, tenant.demo, refresh.token
demo-hydro-sensor-client
hydro, tenant.demo, refresh.token

Registered devices

Device ID
Allowed to Renew Token
demo.device.01
Yes
demo.device.02
No

Availability

We maintain our demo environment on a "best effort" basis. We are committed to keeping our environment as stable as possible but reserve the right to terminate our demo offer at any time without prior notification.

Update Postman collection

To update our Postman collection open the "Demo" collection and click on the three dots in the top right corner, select "Pull changes".
Next, Postman will display what has changed. Click on "Pull changes" to update the Postman collection.

Security Considerations

In order to simulate an IoT device with our Postman collection, we have to publicly expose the private key in our Postman environment, allowing Postman to generate the JWT to authenticate the demo devices. Both demo devices have registered the same public key.
We strongly advise against ever exposing any private key or using the same key for multiple devices outside the demo environment!