Responses

Info

Normally the server sends a HTTP Response to every Request it receives. Depending on the outcome of the request the response can be different, the use of the different HTTP Resonse codes are described below. Furthermore every response will contain a JSON Payload in it's body wich will look something like this:

{
    "status": 200,
    "content": {"Message": "Ok"}
}

...where the value of status is the same HTTP Response code as the response has as an integer; and the value of data usually contains valuable information (like a small message or description)

Response Codes

• 200 - OK: Indicates the Request was accepted by the server, and appropriate actions have been taken.
• 304 - Not Modified: Indicates the Request was accepted, but no actions are necessary as nothing new has been reported
• 400 - Bad Request: The Request could not be understood by the server.
• 401 - Unauthorized: Either the Auth-Token/User-Token was not provided, not eligible or could not be read
• 404 - Not Found: The Request pointed to a resource that is not existent (this is also sent when an invalid Notification Type is sent)
• 409 - Conflict: Indicates the sent request is conflicting with the current state of the account or server
• 500 - Internal Server Error: Something bad happened on the Server Side, the Request is assumed to be unhandled
• 503 - Service Unavailable: The Server is not available at the moment.