Status Codes

On submitting an API call to the Loyalty Harbor API, you get a response to inform you that whether the request was received and processed or an error occured.

2xx success

  • 200 OK

This is the standard response for successful HTTP requests. The response will contain an entity describing or containing the result of the action

  • 201 Created

The request was processed successful. The response will not contain an entity. In the response header is a field location with an url you can follow to get more information about the resource created.

  • 204 No Content

The request was processed successful. The response will not contain an entity.

4xx client errors

  • 400 Bad Request

The client send an invalid request. Check for mandatory parameters and valid syntax.

  • 401 Unauthorized

The client did not authorize. Provide a JWT while you call this resource.

  • 403 Forbidden

Based on the JWT, the client is not allowed to call this resource.

  • 404 Not Found

The client called an unknown path or passed an unknown path parameter.

  • 405 Method Not Allowed

The client invoked a call with wrong HTTP verb/method.

  • 409 Conflict

There is a conflict in the current state of the resource.

  • 415 Unsupported Media Type

The client invoked a call with an unsupported media type.

  • 422 Unprocessable Entity

The request was syntactically correct but was unable to process due to semantic errors.

5xx server errors

  • 500 Internal Server Error

This is a generic error message.