Login a user

POST 
/users/login

Login a user with the given credentials or create an initial account if the database is empty.

Request

Responses

200

OK. The request was successfully executed. User is logged in.

400

Bad Request. The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). Note, the actual error message may be different from the example one.

401

Unauthorized. The request has not been applied because the user does not have valid authentication credentials for the target resource. Note, the actual error message may be different from the example one.

403

Forbidden. The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). The request should not be repeated. Note, the actual error message may be different from the example one.

406

Not Acceptable. The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

409

Conflict. Indicates that the request could not be processed because of conflict in the current state of the resource.

415

Unsupported Media Type. The request entity has a media type which the server or resource does not support. For example, the client uses the content type: text/plain, but the server requires application/json.

429

Too Many Requests. The user has sent too many requests in a given amount of time.

default

Internal Server Error. A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.