Skip to content
Go to file
Cannot retrieve contributors at this time
238 lines (147 sloc) 11.4 KB

Getting Started with the Thing+ REST APIs

Step 1. Service set up

  • Register a Thing+ service at
    • Or, your service may have already have been set up by our team, if you are a commercial partner
  • If you are making an app, make sure your application can receive web requests from Thing+ (i.e. It has a public IP or URL)

NOTE: Please check your Thing+ service's location before continuing

  • - This is the main API server - if you registered your own service, this will be the API server you should use
  • - This is the EU API server
  • - This is a commercial API test server from Seoul.
  • - If you have signed up for our custom domain service You MUST ensure that you use the correct API server, depending on where your service (SERVICE_NAME.thingplus) is registered

Step 2. Prepare Postman

2.1. Postman for getting started with the Thing+ REST API

2.2. Import a Postman collection

  1. Click the 'Import' button


  1. Select 'Download from link'

import link

  1. Download this

  2. Click 'Import' button and choose the downloaded file

  3. Close the module

2.3. Check the imported collection

  • Select the 'Collections' tab and then select the 'Getting Started with the Thing+ REST API' collection


Step 3. Register Client ID & Client Secret Key with Thing+

This step prepares your application for OAuth. This step does not involve user credentials, all credentials mentioned are for your application. Normally you should only do this ONCE per application, unless your application require complex ACL and roles management

  1. Open Chrome browser then Sign in to the Thing+ Portal

interceptor enable

  1. Launch Postman

  2. Enable interceptor

interceptor enable

  1. Install interceptor

interceptor enable

  1. Set a Client ID and Secret

interceptor enable

  • Select Getting a client ID and secret on the collection
  • Select the Body tab
  • Select raw
  • Put your OAuth client ID in the reqId field. You may choose any ID here - something simple and easy to remember is fine. This should be unique across all applications connected to Thing+.
  • Put your OAuth client secret in the clientSecret field. You may choose anything as your OAuth Client Secret - consider it a password of sorts. These two fields (client ID and Client Secret) should not be exposed to anyone. Keep it secret
  • Put the name of your application into the name field. This is used to identify your application. You should put the name of your company or service here, along with something to make it unique (If Thing+ has any other application with the same name, you will run into an error). For example, leland_0144 is a much better application name then "leland".
  • Change the field scopes to determine the rights for your application. Read more about acceptable scopes here
  • Click the Send button
  1. Result should display 201 Created

interceptor enable

  1. Disable interceptor

interceptor disable

Step 4. Get OAuth Access token with Authorization Code Grant

This step authorizes the user with Thing+ via your application

An Access token Expires in 15 days. This may be changed later without prior notification. Please check back often

  1. Prepare login page for your application
  2. When the user logins, redirect them to this URL{CLIENT_ID}&redirect_uri={REDIRECT_URI}
  • Replace {CLIENT_ID} with the Thing+ OAuth Client ID you used as your reqID in steps 3-1 to 3-6
  • Replace {REDIRECT_URI} with your callback URL. This URL should we able to take a 'code' parameter. For example http://yoururl/?code={AUTHORIZATION_CODE}

OAuth authorization screen

  1. User should click the 'Allow' button

  2. Thing+ will redirect back to your {REDIRECT_URI} with the "code" in your query string interceptor enable

  3. Exchange code for an OAuth Access token

This step should be automated in your code, the method below is for demonstration purpose only

exchange code with postman

  • Select Exchange code for an OAuth Access token from the collection
  • Select Body tab
  • Select x-www-form-urlencoded
  • Add {AUTHORIZATION_CODE} you received from the last step to code field
  • Fill in the client ID for your appliction in client_id
  • Fill in the client secret for your application in client_secret
  • Fill in the redirect URL. This URL should be the same with the redirect URL from step 2
  • Click the 'Send' button
  1. Result should say "200 OK" and provide you with an access_token

interceptor enable

Step 5. Using Thing+ REST API with an OAuth Access token

Step 5-1. Create a Postman Environment

This step is for trying out API with POSTMAN, you can skip this part if you only want to authorize your application

  1. Launch Postman

  2. Select 'Manage environments'


  1. Click the 'Add' button

environment add

  1. Add a 'Key' and 'Value' and Click the 'Submit' button

environment submit

  • Add 'Thing+ production' to 'New environment' field.
  • Add AccessToken (Case Sensitive) to Key field.
  • Add your OAuth Access Token to Value field.
  • Close the dialog
  1. Select 'Thing+ production'


  1. Try sending a request. Now you are ready to use the Thing+ REST API with an OAuth Access token. Your requests should look similar to this

environment variable

Step 5-2. Authorization in your app

This step authorizes your application to use Thing+

When you are sending requests to the Thing+ API, be sure to include the token you acquired from step 4 into the header with

Authorization: Bearer {AccessToken}

Step 6. Learning how the API functions

Now, you should be able to use our API directly in combination with your service.

To start, the API documentation is located HERE.

Note: You must make sure you are using the correct API server location. It will be some variation on api.thingplus.xxxxx. Please see the beginning of this guide for more info.

Note that within each section of the API docs, you will see a summary of the API action, a definition of it (Definition Tab) and a try it out section (Try It Out tab).


In the "Try It Out" section, you will see what a typical request body looks like, as well as the ability to edit the request body, header, etc. and click the "Send Request" button to see what a request using that information would look like, immediately.

Finally, at the bottom of the "Try It Out" section, you will notice a "Code Generation" drop down box - clicking this will allow you to see what the actual code might look like in order to place this request into your own application.


Step 7 Pushing sensor data to your Dashboard

Step 7-1. If you have a physical device

Connect your device to Thing+. We have a detailed list of supported device and connection guide here.

Step 7-2. If you don't have a physical device

This step will walk you through creating Gateway → Device → Sensor

The easiest way to get data flowing to something on the dashboard is create a open source gateway via the UI with the sensor(s) types you would like to test.

  1. Use the create gateway prompt (from the settings menu → gateway management → plus button),
  2. Select "Open Source Gateway v2" from the gateway model menu


  1. Use your PC's MAC address (or any other MAC address) as the gateway ID.
  2. Deselect all sensors. You'll be asked to restart the gateway, choose No
  3. Create a device following step 6 as described here.
  4. Create a sensor following step 7 as described here.

After this is created, you can directly push your data into these sensors via using MQTT. See the guide HERE.

Alternatively, it is possible to directly push sensor data via the REST API using the Update Sensor-series request. However, for anything more then a single data push, MQTT should always be used.

Assuming you were able to send your sensor values via MQTT or HTTPS, you should see the sensor's value changing if you created a sensor widget on the dashboard.

Congrats. :)

Step 8. Tips and Tricks for working with the Thing+ API

Postman lets you generate code snippets in more than 15 languages.

From Writing front-end API code with Postman

Code �generation

Using MQTT to send sensor data/values

Reading gateway information

  • Select Reading gateways in the collection and Click the 'Send' button
  • You can get your gateways's ID
  • Request URL: [GET]
  • Response type is Object.

http header

Reading gateway information including filters

  • Select a Reading gateways on the collection and Click the 'Send' button.
  • Request URL: [GET]
  • Accepted Parameters
  • Response type is Object
You can’t perform that action at this time.