Make PI Web API responses more descriptive or allow developers to configure their own custom response fields.
Currently if a PI Web API user attempts an action which is not allowed, the error handling is somewhat generic.
Stream and Stream Set controller calls might contain an additional information in the response fields, but not always.
e.g. Trying to create a tag using an existing Tag name results in: 409 with error message “An exception has occurred. Please contact your PI Web API administrator for help in enabling debug mode”
Better response codes would allow developers to add custom application logic and inform end users what went wrong in their request.
Sean Lapuk commented
Part of this enhancement would be documentation in the PI Web API Reference for the possible HTTP Response Codes (such as the CreatePoint POST call 409 conflict)