Common Errors
Any errors will appear in the details array of the response JSON, except in specific cases where the the error is a result of the backend not being reached for processing, for example if invalid JSON is received. The details array is appended to in-order during processing. The first error message on the list will describe the problem most accurately and should resolve the cascading error messages beneath it.
The following table described several errors that may be seen across various endpoints, as well as how they may be resolved.
| Code | Description | Resolution |
|---|---|---|
| 400 | The request JSON did not pass schema validation, please ensure the format is correct and try again. | Ensure the JSON request matches the expected schema for the endpoint. Ensure that all data types are correct. |
| 400 | ERROR: The session could not be found. Please ensure the session exists and try again. | Ensure a session was created using the "Create Session" endpoint, and that the correct sessionID was included in the URL. If the session exists, check that the measureID used to create the session is the same as the measureID in this request. |
| 400 | Invalid MeasureID | Verify that the input measureID is correct |
| 404 | Resource not found. | Ensure that the URL being requested is correct. |
| 500 | Internal server error. | Most commonly occurs due to invalid request JSON. Check that the request has no missing commas, brackets are correct, and quotes are escaped as necessary. |