JSON RPC 2.0 and Status codes
Note that unlike e.g. REST APIs, JSON RPC 2,0 does not use HTTP status codes for errors. This is because JSON RPC is transfer protocol agnostic.
This does not mean that transfer protocol errors can not occur and you need to handle them accordingly.
This error is returned if the TOKEN used to access the Clarify API in the
Normal response from the RPC API. This does not mean that the call succeed. Check the response body for errors.
204 No Content
The request reached the RPC API successfully, but did not provide an