The Developer Portal was built to help you manage your applications and the device types associated with them.
If you are testing a new application, you’ll want to maintain two separate accounts, one for each portal. The User Portal lets you simulate a user account and connect a device. The Developer Portal is the home of your official developer account.
Let’s look at the Applications section on the left side of the dashboard. This column summarizes all of the applications you have associated with your user ID. This is the user ID associated with your developer account.
If you click the “VIEW ALL” link beneath your applications, you will be taken to the Applications page. This is also accessible by clicking on “APPLICATIONS” in the top bar. Through this page, you can edit your application info (name, description, redirect URL, OAuth 2.0 flow, permissions and device types) and delete applications.
An important feature of the Applications page is that it lets you find the client ID and client secret of each application. Your application’s client ID is also known as its application ID. Both strings are required when using OAuth 2.0.
To get this information, click on “SHOW CLIENT ID & SECRET” in each application box.
The rest of the Applications interface should be self-explanatory, but see these instructions in the documentation for a step-by-step walkthrough of creating your first application.
Returning to the dashboard, we see that the second column has the same format, but covers device types.
Device types are categories of devices recognized by SAMI. Devices are clients such as sensors, appliances, applications and services. In order to save data in SAMI with your device, you first need to define its device type and Manifest.
Not everyone will need to create a new device type with the Developer Portal. Once a device type is public (see below), anyone can implement a device with the same characteristics.
On the Device Types page, you can see that each Device Type has a STATUS and a VERSION. The version corresponds to the Manifest version associated with your device type. By clicking the “DETAILS” link to the right, you can submit a new Manifest version.
On this page, you can click the button to “Add New Version” and paste your new Manifest in the box on the next page. Doing so will automatically move the device type to the next version, although the Manifest will need to be approved again. See the documentation for more information on the recommended format and verification process for new Manifests.
Finally, on this page you can also choose to “PUBLISH” your device type if it has a PRIVATE status. This will make your device type available to all developers on SAMI, which is why you should make sure your Manifest is clean, efficient and thoroughly tested—a good rule for everything else you might do!
Top image: Sonny Abesamis