Errors
All RESToverHTTP error responses follow the same basic format. An Error object is returned in response to an erroneous RESToverHTTP request, accompanied by an HTTP status code of 400.
Specific error codes are listed with each RESToverHTTP endpoint.
An example of an erroneous Response message
{
"code": 1002,
"message": "Invalid enumeration set value",
"data": {
"member": "side",
"value": "CROSS"
}
}
The Error object is expressed as a single JSON Object, with the following members:
Member | Type | Req | Description |
|---|---|---|---|
code | number | Y | The type of error that occurred. |
message | string | Y | A short description of the error. |
data | object | N | Additional structured information about the error. The value is determined by the specific member invoked and may not be present if the error does not require it. |
The following general error codes are supported by Paradigm:
Code | Message | Meaning |
|---|---|---|
-32700 | Parse error | Invalid JSON received by the server. |
-32600 | Invalid Request | The JSON sent is not a valid Request object. |
-32601 | Method not found | The method does not exist / is not available. |
-32602 | Invalid params | Invalid method parameter(s). |
-32603 | Internal error | Internal JSON-RPC error. |
429 | Desk's ratelimit reached. Expected available in 1 second. | Refer to Rate Limit section above. |
1001 | Insufficient permissions | The user does not have sufficient permissions to execute the method. |
1002 | Invalid enumeration set value | The enumeration set value is invalid for the specified field. |
Last modified 4mo ago