Response Code | Code Description | HTTP Status Code | Details |
---|---|---|---|
UT-0400 | Bad Request | 400 | The request could not be processed by the server due to incorrect syntax. API commands can be accessed with this format:
If you encounter this error, ensure the referencing URL is correct. |
UT-0404 | Resource Not Found | 404 | The request could not be processed because an object is missing. The endpoint may have been omitted from the command, or was spelled incorrectly. |
UT-0405 | Method Not Allowed | 405 | The user does not have permission to perform the requested action. The user's up.time permissions (for example, not permitted to Add Elements, Edit, or Delete Elements) stops them from doing the same though the API (POST, PUT, DELETE, respectively). |
UT-0500 | Unknown | 500 | The corresponding HTTP error code (500) is a catch-all error generated by the Web server where an unexpected condition prevented the request from being fulfilled. View the |
UT-0555 | Unknown Exception | 500 | The corresponding HTTP error code (500) is a catch-all error generated by the Web server where an unexpected condition prevented the request from being fulfilled. In this case, an exception has occurred; as a starting point, look for this exception in the |
UT-0560 | Internal Server Error | 500 | The corresponding HTTP error code (500) is a catch-all error generated by the Web server where an unexpected condition prevented the request from being fulfilled. In this case, an exception caused a stack trace; as a starting point, look for this stack trace in the |