API Guide

Get first four
devices from the
Device collection
/api/DeviceService/Devices?$top=4
NOTE: For more information about $skip and $top, see OData Version 4.0 Part 1: Protocol at docs.oasis-open.org.
Request headers
The request header represents headers in the client HTTPS request that are used to communicate client-preferences to the
service end point. The service provides the supported preference in the response header.
The following table lists a few examples of request headers:
Table 4. Examples of request headers
Request Header Description Example
x-auth-token Authentication token taken from
the return header of the
SessionService/Sessions POST
operation to create a session.
x-auth-token: d6399a19-38c8-467b-
a1ec-75ffa03efb7c
Accept-Language Choice of language that the client can
request—Optional.
Accept-Language: en
Response codes
For synchronous operations, the server returns HTTP response codes 200 or 204. For operations that take a long time, the
server returns a status code of 202 along with an HTTP response header (Location). This response corresponds to the URI of
the temporary resource that can be used to monitor the operation.
The following table lists some of the response codes:
Table 5. HTTP response codes
Request Response code
Success codes
GET
● 200 – OK with message body
● 204 – OK with no message body
● 206 – OK with partial message body
POST
● 201 – Resource created (operation complete)
● 202 – Resource accepted (operation pending)
PUT
● 202 – Accepted (operation pending)
● 204 – Success (operation complete)
DELETE
● 202 – Accepted (operation pending)
● 204 – Success (operation complete)
Failure codes
Invalid parameter 400 - Invalid parameter
Authorization 401 - Authorization failure
Permission denied 403 - Permission denied
Not found 404 - Resource not found
Invalid request method 405 - Invalid request method
Internal server error 500 - Internal server error
14 Key integration concepts