Errors allow you to simulate receiving a number of possible error messages. This is especially helpful for seeing how your application responds to different error messages as well as quickly learning all the possible errors that may be returned from the APIs.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Simulate Echo error responses so you can test your integration's error handling.
Use this endpoint to confirm that your client handles common error payloads before you encounter them in resource APIs. To test connectivity, credentials, or input formats instead, see Testing & Debugging Overview.
The endpoint can return simulated error conditions for supported HTTP-style error codes.
Resource URI
GET /rest/echo/errorsExample
GET /rest/echo/errorsA successful response returns a standard success payload.
{
"status": "success",
"count": 1,
"type": null,
"results": [
"success"
]
}Simulated error responses use the standard Error response shape with fields such as code, message, objectName, and propertyName. For error payload details, see Responses.
{
"status": "error",
"count": 2,
"type": "Error",
"results": [
{
"code": "400",
"message": "Bad Request",
"objectName": "http"
}
]
}For the full set of Echo testing endpoints, see Testing & Debugging Overview.