Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Return useful error information

Log in to subscribe to topics and get notified when content changes.

Return useful error information

Provide the client with enough information in error messages to allow them to understand the problem without having to refer to your API documentation.

An error response should include a helpful error message, as well as an error status code.

For example, when a client queries a record that does not exist, you can return the error message "The specified record does not exist. Ensure that a record with the ID of <id value> exists in the application." along with a 404 status code.

The Scripted REST APIs feature includes several preconfigured error objects you can use for commonly-encountered errors, and a customizable ServiceRequest error object you can use when the preconfigured error objects do not meet your needs.