OAuth Authorization Code

Management and Data Reporting for Electronic Temperature Sensors Developer Guide

Management and Data Reporting for Electronic Temperature Sensors Developer Guide
Overview
- Workflow
Getting Started
- API Authentication
  - Using a Simple Key
    - OAuth Client Credentials
    - OAuth Authorization Code
Enrolling Devices
- Enrolling a ZS300 Sensor
Listing the Sensors
- Listing the ZS300 Sensors
Creating a Task
Associating a Sensor with a Task
- Associating a Sensor with a Task
Performing a Simple Task
- Stopping a Task
Using Webhook Subscriptions
Displaying Full Event Record for Task ID
- Using the Developer Portal Interactive Documentation
  - Sorting, Filtering, and Pagination
- Using an API Test Tool
Downloading AIDL Files

The primary method for creating a customer-specific Bearer token is the Authorization Code grant type. This is the standard 3-legged OAuth used in many web applications. It is considered one of the most secure methods of getting a token. All Zebra Bearer tokens last for one hour but can be refreshed using the previous token.

Authorization code grant type is a multi-step process. First you redirect to the IDP login and provide a redirect URI. After the customer logs in, the IDP will send the authorization code to the client app URI. Authorization codes last for 10 seconds. The client app calls the token API with the code to get a bearer token.

Go to developer.zebra.com/apis/oauth-authorization-code-0 for more information on OAuth Authorization Code.