IoT-Ticket.com. Your Ticket to the Internet of Things and beyond. IoT API

Transcription

1 IoT-Ticket.com Your Ticket to the Internet of Things and beyond IoT API

2 Contents 1 Introduction Overview Abbreviations and definitions Data Model General Information Communication Security Quota Policy Device Management Register a device Get devices Get a device Get device datanode list Reading and Writing Data Data types Writing data Reading data Example of a device with hierarchical components Error Handling Quota Management Get overall quota Get device specific quota Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 2 / 29

3 List of figures Figure 1 WRM IOT Data model hierarchy Figure 2 New Device under Enterprise Figure 3 Device Registration and data saving sequence Figure 4 Aircraft Model Figure 5 Error code and their meanings List of Tables Table 1 Response to register device Table 2 Response to get devices Table 3 Response to get a device Table 4 Response to get device datanodes Table 5 Response to write to device s datanodes. Table 6 Response to read device s datanodes. Table 7 Aircraft Measurement point sample Table 8 Error codes Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 3 / 29

4 1 Introduction 1.1 Overview This document provides the documentation for the WRM Internet of Things Rest API. It explains how devices are created and managed, how data nodes are created, written to and read from. While the examples provided are not exhaustive in scope, they do provide a clear indication of what is expected as input and output to the API. 1.2 Abbreviations and definitions Concept REST API JSON XML IoT Description Representational state transfer Application Programming Interface JavaScript Object Notation Extensible Markup Language Internet of Things In the document, an integer type refers to a 32 bit signed integer ( to ) and a long is a 64 bit signed integer ( to ). The length of strings accepted as parameter to a call are stated in the form String:(max-length) meaning the string should not exceed max-length characters. Only UTF-8 encoded strings are accepted. 1.3 Data Model The WRM system data model visible through this REST API is illustrated in Figure 1. At the root level of this model are Enterprises (e.g. companies or customers). Each Enterprise can have multiple devices that need to be monitored (e.g. a home, an engine, or a truck). A device can have multiple Data Nodes, describing what is measured from the device it belongs to (e.g. temperature, engine RPM). Enterprise Device Data node Figure 1 WRM IOT Data model hierarchy Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 4 / 29

5 1.4 General Information In the examples that will follow, server-url stands for a URL provided for the WRM instance to which the API calls are to be made and the version number. i.e. server-url = {base-url}/api/v{version-number} By default the complete api url will be Communication Security All requests to the API are made through HTTPS. With HTTPS, the HTTP protocol is protected from wiretapping and man-in-the-middle attacks therefore data being transferred is secure. Authentication to the API will be via HTTP Basic with username and password pair and should be sent along all requests that require it. Below is an example of a request using command line program curl. The user name and password are supplied with the user option. curl -X POST --user wrmuser:wrmpassword \ -H "Content-Type:application/json" \ -d '{"name":"opc Server", "manufacturer":"hp", "type":"pc", "attributes":[{"key":"os","value":"windows 7"}, {"key":"screen-size","value":"1960*1800"}] }' \ " 1.6 Quota Policy WRM limits the number of requests per day, amount of data that can be stored, number of devices and number of data node per device. Each of these quotas is enforced on a per-client basis. Users should visit the WRM webpage on how to increase allocated quotas. Subject to change, free users are currently restricted to five devices, a maximum of 20 data nodes per device and a total of 20,000 read request per day per device. The total amount of data storage for a free user is also restricted to 50 Megabytes. When the quota is exceeded, an HTTP Response code 403 with the specific error code is sent in the response. For more details see the Error Handling chapter. The read request quotas are reset at midnight, UTC time. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 5 / 29

6 2 Device Management A registered user by default has an enterprise root object. When a device is registered with a client s credential it immediately shows up under the client s enterprise. See Figure 2. User's Enterprise New Device Figure 2 New Device under Enterprise A device Id is automatically assigned to a newly registered device; the API Client should store this device Id as it uniquely identifies the device and will be used in subsequent calls. Client should avoid multiple registration call as this might result to duplicate devices being created. When in doubt, a good flow will be to get the list of already created devices and validate the device s existence on the server through its name and attributes. Once the device is registered and the device id is obtained, clients can immediately start sending measurement values to the server. Figure 3 illustrates this sequence. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 6 / 29

7 Figure 3 Device Registration and data saving sequence 2.1 Register a device URL: /devices/ HTTP method: POST Authentication Required: Yes This call will create a new device under the authenticated client s enterprise. Parameter Description Example Object A Json object with the following fields: name (required) manufacturer (required) type description attributes Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 7 / 29 { "name": "OPC Server", "manufacturer": "HP", "type": "PC", "description": "The main server for process data", "attributes":[{ "key":"application Version",

8 name (String: 100) manufacturer (String:100) Type (String:100) description (String:255) Attributes (key,string:255) (value,string:255) This short name for the device. It is visible in the enterprise tree when client logs in to the WRM Desktop. Short name for the device manufacturer This field should describe the main category the device belongs. A description of the device. What it does or where it s located. Contains arrays of key value pairs. This is used to store additional attributes for the devices as desired by the client. A maximum of 50 attributes is accepted. "value": "0.2.3"}, {"key":"chip","value":"corei7"}] } NX100, IPhone5 ABB, Apple PC, Server, MobilePhone, Sensor, Vehicle Frequency converter for the ship s engine. Additional attributes for an AC Drive may include. Inputphase : Three phases InputVoltage: V Options:EMC2,QPES When any of the required fields are not present or the parameter constraints are violated, an HTTP status code 400 is returned along with an error object in the response payload. For more details see the Error Handling chapter. Table 1 Response to register device Field href deviceid name Description URL to access the resource The id of the device, to be used in subsequent calls to write and read the device data nodes. It consists of 32 alphanumeric characters. The name provided for the device when registering it. manufacturer The manufacturer name provided when registering. type createdat attributes description The type provided for the device when registering it. The time the device was created on the server. The ISO8601 format (UTC) format is used. The device attributes. Name value pair provided when registering the device. Description of the device if any. Example Request Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 8 / 29

9 REQUEST PAYLOAD is as shown in the example above. JSON Response { } "attributes": [{ "key": "Application version", "value": "0.2.3" }, { "key": "Chip", "value": "Corei7" }], "createdat": " T10:31:05UTC", "deviceid": "153ffceb982745e8b1e8abacf9c217f3", "href": " "name": "OPC Server", "manufacturer": "HP", "type": "PC" 2.2 Get devices Returns a list consisting of general information about devices the client has access to. URL: /devices HTTP method: GET Authentication Required: Yes Parameter Description Example callback JavaScript function to be executed when the response is received (JSONP) /devices?callback=foo returns: foo(response data); format Format (json or xml) default is json /devices?format=xml limit (integer) offset (integer) Number of results to return. Maximum of 100, defaults to 10 when none is provided Number of result to skip from the beginning. /devices?limit=5 /devices?offset=3 Paging example: /devices?offset=0&limit=100 /devices?offset=100&limit=100 When any of the required fields are not present or the parameter constraints are violated, an HTTP status code 400 is returned along with an error object in the response payload. For more details see the Error Handling chapter. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 9 / 29

10 Table 2 Response to get devices Field Description offset Number of results skipped from the beginning limit Amount of results per page fullsize The total number of devices that the client has access to. devices List of device object. Each of the object contains href name manufacturer type (if any) createdat description attributes href URL to the device name Name of the device provided when registering it. manufacturer The manufacturer name provided when registering. type The type of the device provided when registering it. createdat The time the device was registered using ISO8601 format. description Description of the device if any. attributes The device attributes. Name value pair provided when registering the device. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 10 / 29

11 Example Request REQUEST PAYLOAD:NONE JSON Response { } "fullsize": 28, "limit": 10, "offset": 0, "items": [ { "attributes": [{ "key": "OS", "value": "Windows 7" }, { "key": "Screen Size", "value": "30 Inches" }], "createdat": " T10:31:05UTC", "deviceid": "153ffceb982745e8b1e8abacf9c217f3", "href": " "name": "OPC Server", "manufacturer": "HP", "type": "PC" }, { "attributes": [], "createdat": " T08:55:14UTC", "deviceid": "e057aba9cad84a3aa3fc6b99bbe2196e", "href": " "name": "GT-I9295", "manufacturer": "Samsung", "type": "MobilePhone" },... ] <devicesresult> <fullsize>28</fullsize> <limit>10</limit> <offset>0</offset> <items> <device> <attributes /> XML Response <createdat> t10:40:17utc</createdat> <description>the main server for process data</description> <deviceid>e057aba9cad84a3aa3fc6b99bbe2196e</deviceid> <href> <name>gt-19295</name> Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 11 / 29

12 <type>mobilephone</type> <manufacturer>samsung</manufacturer> </device> <device> <attributes> <attribute key="application Version" value="0.2.3"/> <attribute key="chip" value="corei7"/> </attributes> <createdat> t10:44:03utc</createdat> <description>the main server for process data</description> <deviceid>153ffceb982745e8b1e8abacf9c217f3</deviceid> <href> <name>opc Server</name> <type>pc</type> <manufacturer>hp</manufacturer> </device> <!--more devices --> </items> </devicesresult> 2.3 Get a device URL: /devices/deviceid HTTP method: GET Authentication Required: Yes Get general information for the device with the provided id. Parameter Description Example callback JavaScript function to be executed when the response is received (JSONP) /devices/deviceid?callback=foo returns: foo(response data); format Format (json or xml) default is json /devices/deviceid?format=xml When any of the required fields are not present or the parameter constraints are violated, an HTTP status code 400 is returned along with an error object with more information. See the Error Handling chapter. Table 3 Response to get a device Field href name type Description URL to the device Name of the device provided when registering it. Type of the device provided when registering it. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 12 / 29

13 manufacturer Manufacturer name provided when registering. createdat description attributes The time the device was registered using ISO8601 format. Description of the device provided. The device attributes. Name value pair provided when registering the device. Example GET Request REQUEST PAYLOAD:NONE JSON Response { } "attributes": [], "createdat": " T08:55:14UTC", "deviceid": "e057aba9cad84a3aa3fc6b99bbe2196e", "href": " "name": "GT-I9295", "description": "The main server for process data", "type": "MobilePhone", "manufacturer": "Samsung", XML Response <device> <attributes> <attribute key="application Version" value="0.2.3"/> <attribute key="chip" value="corei7"/> </attributes> <createdat> t10:44:03utc</createdat> <description>the main server for process data</description> <deviceid>153ffceb982745e8b1e8abacf9c217f3</deviceid> <href> <name>opc Server</name> <type>pc</type> <manufacturer>hp</manufacturer> </device> 2.4 Get device datanode list URL: /devices/deviceid/datanodes/ HTTP method: GET Authentication Required: Yes Get a list of provided device data nodes Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 13 / 29

14 Parameter Description Example callback limit (integer) offset (integer) JavaScript function to be executed when the response is received (JSONP) Number of results to return. Maximum of 100, defaults to 10 when none is provided Number of result to skip from the beginning. /devices/deviceid/datanodes?callback=foo returns: foo(response data); /devices/deviceid/datanodes?limit=5 /devices/deviceid/datanodes?offset=3 format Format (json or xml) default is json /devices/deviceid/datanodes?format=xml When any of the required fields are not present or the parameter constraints are violated, an HTTP status code 400 is returned along with an error object in the response payload. For more details see Error Handling chapter. Table 4 Response to get device datanodes Field offset limit fullsize items Description Number of results skipped from beginning Amount of results per page Total number of hits to the query. List of data node object Example { GET Request "fullsize": 2, "limit": 10, "offset": 0, "items": [ { "unit": "c", "datatype": "double", REQUEST PAYLOAD:NONE JSON Response "href": " }, { "name": "Temperature", "path": "Engine/Core" Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 14 / 29

15 "unit": "Hz", "datatype": "long", "name": "Cycles", } }] <datanoderesult> <fullsize>2</fullsize> <limit>10</limit> <offset>0</offset> <items> <datanode unit="c"> <datatype>double</datatype> XML Response "href": " <href> f> <name>temperature</name> <path>engine/core</path> </datanode> <datanode unit="hz"> <datatype>long</datatype> <href> <name>cycles</name> </datanode> </items> </datanoderesult> Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 15 / 29

16 3 Reading and Writing Data Data values are written to the device s data nodes. Each data node is identified by its name and the path specified by the client. The data node is created the first time it is encountered by the server. Intermediate nodes are also created if a path is specified the first time the data node is encountered. The full path to the data node should be specified when the data node is to be read from. 3.1 Data types Data Node Data type Type field in response Format Double (64bits) Long ( to ) 64bits double long Numerical value Numerical value String string Any Unicode character except or \ which are escaped by \ Boolean boolean true or false without quotes Binary binary Base64 encoded 3.2 Writing data URL: /process/write/deviceid/ HTTP method: POST Authentication Required: Yes Write the provided values to the corresponding data node. A new data node is created when the server has not received value prior to this with the same name and path if any. Subsequent writes always include the same name and path to write to the same data node. Parameter Description Example deviceid Data to be written The target device id. Arrays of data object to be saved. Each of the object as the following attributes. name (required) path (optional) v- value (required) ts unix timestamp (optional) Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 16 / 29 [{ "name": "Temperature", "path": "MainEngine/Core", "v": 60, "ts": , "unit": "c"}, {"name":"latitude","v":63,

17 unit (optional) datatype (optional) "datatype":"long" }, {"name":" Latitude ","v": 65}, {"name": " Latitude ","v": 67}] Name (string:100) Path: (String:1000) A short description of the datanode. A device s data node is uniquely identified with its name and path. Case insensitive Forward slash separated list of path to be created to get to the datanode. The path can only consist of a maximum of 10 components. A slash at the beginning is simply ignored i.e. the path /Engine/Cabin and Engine/Cabin is equivalent to each other. When viewed from the WRMDesktop UI intermediate nodes as specified by the path are created between the devices and the data node in a nested tree structure. Each component of the path can only contain alphanumeric values A-Za-z0-9.Case insensitive An empty path or a missing path attributes are equivalent to each other. Engine/Cabin/ Example of an invalid Path 1/2/3/4/5/6/7/8/9/10/11 v unit (String:10) ts (long) datatype The value to be written. This must be applicable to the datatype if provided. Unit associated with the data. Preferably 1 or 2 characters. Unix Timestamp. Number of milliseconds since the Epoch. When a timestamp is missing, the current timestamp is automatically used. When datatype is not provided,the possible data type is inferred from the value first received by the server. c,hz Possible values are: long, double, boolean, string or binary. It is case Insensitive. When any of the required fields are not present or the parameter constraints are violated, an HTTP status code 400 is returned along with an error object in the response payload. For more details see the Error Handling chapter. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 17 / 29

18 Table 5 Response to write to device s datanodes. Field writeresult object totalwritten href Description Array of response objects, each containing. href writtencount Total number of data points written URL to read from the data node targeted in the write. writtencount The number of values written to the particular data node Example {"writeresults": [{ POST Request REQUEST PAYLOAD as shown in example above. JSON Response "href": " ", { }, "writtencount": 1 "href": " } ], } "writtencount": 3 "totalwritten": 4 XML Response <writeresults> <writeresult> <href </href> <writtencount>1</writtencount> </writeresult> <writeresult> <href> </href> <writtencount>3</writtencount> </writeresult> <totalwritten>4</totalwritten> </writeresults> Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 18 / 29

19 3.3 Reading data URL: /process/read/deviceid/ HTTP method: GET Authentication Required: Yes Read device data node values. Parameter Description Example format Format (json or xml) default is json /process/read/deviceid?datano des=latitude?format=xml deviceid datanodes The target device id. Comma separated data node names or fullpaths to be read from. If the name provided matches more than one datanode, they are all included in the response. The number of datanodes in the path should not exceed 10. /process/read/deviceid?datano des=latitude,longitude,altitude If there are multiple data node with the same name, include the path to be more specific. For example two datanodes with name Temp with path Engine/core and with no path. The specific read path will be?datanode=/engine/coretemp and?datanodes=/temp respectively. The read path?datanodes=temp will return results for both datanodes. fromdate (long) todate (long) limit (integer) order Unix Timestamp. Number of milliseconds since the Epoch. Defines the time from which the data is obtained.should be provided if there is a todate. Unix Timestamp. Number of milliseconds since the Epoch. Defines the time to which the data read ends. Defaults to current time if not provided and a fromdate exists. If neither the fromdate and todate is provided, the latest value is returned. The maximum number of data points returned for each datanode queried. Defaults to 1000 if not provided and as a maximum of 10,000 values. Orders the values by timestamp either in ascending or descending order. Possible values are ascending and descending. Default is ascending. /process/read/deviceid?datano des=longitude?fromdate= /process/read/deviceid?datano des=longitude?fromdate= &todate= /process/read/deviceid?datano des=longitude?limit=3 /process/read/deviceid?datano des=longitude?order=descendi ng Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 19 / 29

20 When any of the required fields are not present or the parameter constraints are violated, an HTTP status code 400 is returned along with an error object in the response payload. For more details see the Error Handling chapter. Table 6 Response to read device s datanodes. Field readresult Object name path v ts unit Description Array of objects containing o name o type o unit o value object containing arrays of v and ts fields The name of the data node The path to the data node if any. The value at timestamp ts. The timestamp associated with the value. This is always added even if the client did not include a timestamp as at the time of writing. The unit associated with the data node. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 20 / 29

21 Example GET Request Latitude&fromdate= &limit=3 { " datanodereads": [{ }, { }], "name": "Latitude", "datatype": "long", "values": [{ REQUEST PAYLOAD: NONE JSON Response "name": "Temperature", "path": "Engine/Core", "unit": "c", "datatype": "double", "values": [ "v": "60","ts": }] {"v": "65","ts": }, {"v": "63","ts": }, {"v": "73","ts": }] "href": " Latitude&fromdate= &limit=3" } <readresults> XML Response <href> Latitude&fromdate= &limit=3</href> <datanodereads datatype="long"> <name>latitude</name> <values> <value> <v>60</v> <ts> </ts> </value> </values> </datanoderead> <datanoderead unit="c" datatype="double"> <name>temperature</name> <path>engine/core</path> <values> Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 21 / 29

22 <value> <v>65</v> <ts> </ts> </value> <value> <v>67</v> <ts> </ts> </value> <value> <v>73</v> <ts> </ts> </value> </values> </datanoderead> </readresults> 3.4 Example of a device with hierarchical components A device with hierarchical components can be easily modelled using the data node s path. Such a structure is illustrated here with a contrived example of an aircraft with a main and auxiliary engine. The temperature and airflow in the main engine are to be measured while the RPM and temperature in the auxiliary engine are measured. The aircraft also has a latitude and longitude measurement reading as shown in Figure 4 below Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 22 / 29

23 Figure 4 Aircraft Model First the device is registered with the name Aircraft and manufacturer Boeing for example. After which a device Id is obtained and stored. With the device Id, the main engine core temperature is written to a data node named Temperature with path MainEngine/Core. The auxiliary core temperature is written to a data node named Temperature also but with path Auxiliary/Core while the aircraft Latitude is named Latitude with no path provided as listed in Table 7 below. Table 7 Aircraft Measurement point sample Measurement Point Name Path MainEngine Core Temperature Temperature MainEngine/Core AuxiliaryEngine Core Temperature Temperature AuxiliaryEngine/Core Latitude Latitude Similarly the Airflow and RPM are written with the same name but to path MainEngine/Core and Auxiliary/Core path respectively. To read a particular data node values the full path to the data node, {PATH} /{NAME}, should be provided, therefore to read the main engine core temperature for example, the url to use is /process/read/deviceid/?datanodes=mainengine/core/temperature. To read the main engine core temperature, latitude, longitude and auxiliary RPM data nodes; the url to use is Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 23 / 29

24 /process/read/deviceid/?datanodes=mainengine/core/temperature,latitude,lo ngitude,auxiliaryengine/core/rpm. The data nodes could as well be named MainEngineCoreTemperature, AuxillaryEngineCoreTemperature for example, however this does not lean itself to aggregate queries and viewing the aircraft nested structure in the WRMDesktop UI. An example of an aggregated query will be to read all data nodes named temperature for the device. Using the url /process/read/deviceid/?datanodes=temperature the server will return the values for both the Main Engine and Auxiliary Engine core Temperature data nodes. It should be noted that aggregated write request is not allowed, the path must always be specified if any. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 24 / 29

25 4 Error Handling Errors to the API are as a result of invalid credentials, unauthorized access to the target resource, data format issues and sometimes internal server problems. Nonetheless the API always returns one of the following HTTP Status Code. 200 OK Created 400 Bad Request 401 Unauthorized 403 Forbidden 500 Internal Server error. In addition to checking the HTTP Status, developers should also view the response body entity that will describe the error further if any of the status above is received except the OK status. Field description (String:500) code (int) moreinfo (String:255) apiver (int) Description This field provides a general description of the error. See Table 8 for the codes and their meaning. This field points to the documentation url where more description about the error code can be found. The api version number. Example Error response Response (HTTP STATUS 400) { "description":"request cannot be processed because you have exceeded the limit of 30 Megabytes. Visit the WRM website to increase your allotted storage size", } "code":8002, "moreinfo":" "apiver":1 Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 25 / 29

26 Table 8 Error codes code Implication 8000 Internal server error Permission on requested resource is not sufficient 8002 Quota violated 8003 Bad Parameters provided 8004 Write failed. Figure 5 Error code and their meanings Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 26 / 29

27 5 Quota Management When the client quota is exceeded, the API will return an http response 403 Forbidden even though the request is valid. A message object is also returned that includes specific detail on which aspect of the quota has been violated. Note that in calculating storage size, 1 Megabyte of data is regarded as bytes and only the size of the values are calculated in the quota. 5.1 Get overall quota URL: /quota/all HTTP method: GET Authentication Required: Yes Returns an overview of the client s resource usage i.e. how much resource has been used and the maximum amounts allowed. Parameter Description Example callback JavaScript function to be executed when the response is received (JSONP) /quota/all?callback=foo returns: foo(response data); format Format (json or xml) default is json /quota/all?format=xml Field totaldevices (integer) maxnumberofdevices (integer) maxdatanodeperdevice (integer) usedstoragesize (long) maxstoragesize (long) Description Total number of devices the client owns. NOTE: This is not the same as the total number of devices the client has access to. The maximum number of devices the client can create. The maximum of number of device allowed for client per data node. The total size in bytes that the client has written to the server. The maximum size in bytes that the client has a right to write to the server. Example Request REQUEST PAYLOAD:NONE JSON Response Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 27 / 29

28 { } "totaldevices": 3, "maxdeviceallowed": 5, "maxdatanodeperdevice": 10, "usedstoragesize": , "maxstoragesize": XML Response <quota> <totaldevices>3</totaldevices> <maxdeviceallowed>5</maxdeviceallowed> <maxdatanodeperdevice>10</maxdeviceperdatanode> <usedstoragesize> </usedstoragesize> <maxstoragesize> </maxstoragesize> </quota> 5.2 Get device specific quota URL: /quota/{deviceid} HTTP method: GET Authentication Required: Yes. Parameter Description Example callback JavaScript function to be executed when the response is received (JSONP) /quota/all?callback=foo returns: foo(response data); format Format (json or xml) default is json /quota/all?format=xml Field totalrequesttoday (integer) maxreadrequestperday (integer) numberofdatanodes (integer) storagesize (long) deviceid (String:32) Description Total number of request made to the API to the device. Any serviced url that includes the device Id is added to this count. The max number of read request allowed to the client for this device. The number of data node created for the specified device. The total size in bytes that the client has written to the server for the specified device. The device id. Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 28 / 29

29 Example Request REQUEST PAYLOAD:NONE JSON Response { "deviceid":"258d5f5cf f7b754c25dae257" "totalrequesttoday": 5000, "maxreadrequestperday": , "numberofdatanodes": 5, "storagesize": 3072 } XML Response <devicequota> <totalrequesttoday>5000</totalrequesttoday> <maxreadrequestperday>100000</maxreadrequestperday> <deviceid>d dd460ea1de7e5bda047b08</deviceid> <numberofdatanodes>5</numberofdatanodes> <storagesize>3072</storagesize> </devicequota> Filename: IoT-Ticket.com REST API.docx Version: 1.1 Page: 29 / 29