...
As with the standard flow, the API responds with errors when the session limit is reached or there are authentication errors.
The session ID must be globally unique for the given user, so if the client attempts to create a new session through a PUT request and it already exists for some other user, then the API will respond with a 404 - Not found errorsame session ID is used for two separate sessions for the same user, there will be a conflict.
If the API is called with a PUT request for a session ID that already exists, but the body of the request contains a device type that conflicts with the previously created session, then the API will respond with a 409 - Conflict error.