Actions
Feature #16160
open
REST API should return 409 Conflict if User/Project/etc already exists
Status:
New
Priority:
Normal
Assignee:
-
Category:
REST API
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Description
The REST API returns nearly always 422 Unprocessable Entity and details the errors in the response e.g. like "User Id already exists"
For remote integrations more different error codes would make life easier.
E.g.
POST /users to create a user entity
--> 201 Created if OK
--> 409 if Username already taken
--> 422 if input data incompleteCurrently the response has to be examined (it is localized) which is a bad pattern of course.
No data to display
Actions