belaie | 2016-09-11 10:37:12 UTC | #1
We have been doing identity management integeration for purecloud from a vendor "NetIQ identity manager" by their REST connector. Unfortunatly the connector expects successfull create user operations should return http status 201, where as purecloude Create User api returns http status 200
PureCloud User api:
/api/rest/v2/users/index.html
NetIQ believes that it is a bug on purecloud side, and they should fix it
NetIQ discussions forum: https://forums.netiq.com/showthread.php?56528-NetIQ-REST-driver-returns-status-error-on-add-user
I have checked REST service specification, and it looks like NetIQ is correct,
http://www.restapitutorial.com/lessons/httpmethods.html
Whats the deal? :slight_smile:
tim.smith | 2016-09-02 15:42:48 UTC | #2
They're not wrong that 201 is a suitable response code for a POST request. However, per RFC 2616, 200 is a valid well. It explicitly provides an example of using 200 for a POST response with a body that is "an entity describing or containing the result of the action". So while 201 would be a more specific response code here, 200 is also correct.
Changing the response code would be considered a breaking change because it would change the behavior of the API and it is not a bug (based on the RFC). So this cannot not be changed for v2. If you'd like, you can post this request to the API Enhancement Requests topic for consideration in the next major version of the API.
system | 2017-08-28 19:26:58 UTC | #3
This post was migrated from the old Developer Forum.
ref: 361