| 200 | Generic OK response |
| 201 | OK response when a new entity is created and the id is returned, e.g. a new order or a new trader |
| 202 | Processing of the request is handled offline or later. We don't yet know if it will succeed or not. |
| 204 | OK response. No body in the response. |
| 400 | The request is malformed e.g a syntax error, or some other validations fails |
| 401 | Unauthorised. API key is not valid or the email/password is wrong |
| 403 | Forbidden. API key is valid but permissions are not right |
| 409 | Conflict. For example, when updating a Term with a name that is already taken by another term |
| 422 | Syntax is correct, but the validation fails. For example, when an email address is malformed |
| 500 | Catch all error used for any other error than the ones listed above |
