API Guide

Request header Description
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
Service unavailable 503 – Service unavailable
Response headers
The following table includes a few examples of response headers. For an extensive list of response headers, see List of HTTP header
fields.
Table 4. Response headers
Response header Description Example
Connection Control options for the current
connection and list of hop-by-hop
request fields.[8]
Must not be used with HTTP/2.[9]
Connection : Keep-Alive
Content-Type Specifies the format of the content
that is returned by the server. If there
are multiple formats that could be
accepted in the client request (using
the Accept header), the server
chooses the appropriate supported
format.
Content-Type: application/json; odata.metadata=minimal
Keep-alive The timeout header parameter
indicates the time that a connection
will be allowed to remain idle before it
is closed.
The max header parameter indicates
the maximum number of requests
that will be permitted before the
connection is closed.
Timeout=5; max=150
Content-length The length of the request body in
octets (8-bit bytes).
Content-Length: 348
date The date and time that the message
was originated (in "HTTP-date"
date: Thu, 02 Apr 2009 11:11:28
GMT
8 Key integration concepts