Web Procotols
JSON-RPC
Grove API supports all blochchains that use the JSON-RPC 2.0 Specification.
With the implementation of PATH, Grove has implemented an opinonated implementation of HTTP Status codes on JSON-RPC:
JSON-RPC to HTTP Status Code Mapping
It's common practice in JSON-RPC-over-HTTP implementations to map:
Client errors(e.g., -32600Invalid Request) to4xxHTTP statusesServer errors(e.g., -32603Internal erroror -32000 "Server error") to5xxHTTP statuses
PATH follows this practice and maps JSON-RPC errors to HTTP status codes as follows:
| JSON-RPC Error Code | Common Meaning | HTTP Status Code |
|---|---|---|
| -32700 | Parse error | 400 Bad Request |
| -32600 | Invalid request | 400 Bad Request |
| -32601 | Method not found | 404 Not Found |
| -32602 | Invalid params | 400 Bad Request |
| -32603 | Internal error | 500 Server Error |
| -32098 | Timeout | 504 Gateway Timeout |
| -32097 | Rate limited | 429 Too Many Requests |
| -32000…-32099 | Server error range | 500 Server Error |
| > 0 | Application errors (client-side) | 400 Bad Request |
| < 0 (other negative) | Application errors (server-side) | 500 Server Error |
REST
Grove API is able to support any RESTful API configuration. Services that utilize a RESTful API will be provided in accordance with their individual specifications.
WebSockets
Coming Soon!