Integrating with a third-party platform in 5 minutes
Before you begin
This guide assumes that you have a Cloud Connector and sensors available. If not, order a Pilot Kit.
Connect the Cloud Connectors
Go right ahead and plug your Cloud Connector into a power outlet.
When the white cloud shines a solid white, you’re connected via the built-in cellular modem and are good to go!
Studio is a developer console where you can manage Sensors, Projects, Service Accounts and more.
Open a new tab, navigate to https://studio.disruptive-technologies.com and login with your user credentials.
All Sensors start their life in the “Inventory” Project when they are shipped. Navigate to it, or another project in which you know you have sensors, by clicking on Manage Projects in the menu on the left and select the project.
Click on Sensors & Connectors in the menu on the left. This will show you a list of all of the Sensors and Cloud Connectors in this Project.
Identify a sensor
To identify the Sensor you have in front of you, press the Identify a Sensor button to the right of the search field at the top. Next press a Sensor, and you will be instantly taken to that Sensors detailed view.
Every time you press the sensor, you should see an animation behind the top Sensor icon, and the last-seen time is updated.
Reliably Streaming Events Using Data Connectors
A Data Connector reliably pushes real-time Sensor data to the endpoints of 3rd party services. There is currently one type of Data Connector, HTTPS Push, which allows you to set up HTTPS POST requests, also known as “web-hooks”, to an endpoint of your choice.
Setting up a Data Connector and Push Data
Click on Data Connectors in the menu and then Add.
For this part, we’ll use the free public messaging service dweet.io. It allows anyone to do a HTTP POST request to an URL with an arbitrary JSON payload and watch for changes in real-time. In other words, it fits our purposes perfectly.
Note that Disruptive Technologies is not affiliated with dweet.io in any way. It is simply a free, hosted, service that fulfills the same role as your server would. If you already have a hosted HTTPS POST endpoint set up, feel free to try to edit the Data Connector to point toward your server instead.
Name the new Data Connector “dweet.io”. The URL needs to be of the format
https://dweet.io/dweet/for/UNIQUE-NAME-HERE, where the all-caps part needs to be unique. For example, use today’s date and append your name, e.g.
Next, check all the check-boxes under EVENTS TO INCLUDE and press SAVE NEW DATA CONNECTOR.
View Real-time Events
Press the Sensor a few times and then go and view the Sensor’s events live at
https://dweet.io/follow/UNIQUE-NAME-HERE, select the Raw tab. Please note that at least one event must have been pushed, or you will get an error saying it doesn’t exist yet.
Press the Sensor, and see the events in real-time.
Until the Sensor sends an event, dweet.io will say “[the] thing isn’t a thing”. This is true for both emulated and physical Sensors, so make sure the Sensor is pressed.
Congratulations, you’ve now managed to integrate your Sensors with a 3rd party service!
Next, in our Interactive API Reference you can explore and test most functionality of the API without writing a single line of code.
You can also take a look at a simple Code Example which sets up a new Project, a Service Account and a small Python client which lists all Devices in the Inventory Project and listens to real-time events from those devices.