Search results
Collection of example OpenRPC documents. Contribute to open-rpc/examples development by creating an account on GitHub.
OpenRPC documents describe a JSON-RPC APIs services and are represented in JSON format. These documents may either be produced and served statically or be generated dynamically from an application. The OpenRPC Specification does not require rewriting existing JSON-RPC APIs.
The OpenRPC Specification defines a standard, programming language-agnostic interface description for JSON-RPC 2.0 APIs.
The OpenRPC Specification defines a standard, programming language-agnostic interface description for JSON-RPC 2.0 APIs.
An object can be specified for use as an HTTP request body with the @Body annotation. The object will also be converted using a converter specified on the Retrofit instance. If no converter is added, only RequestBody can be used. So this is an option using RequestBody and ResponseBody: In your interface use @Body with RequestBody
An OpenRPC document that conforms to the OpenRPC Specification is itself a JSON object, which must be represented in JSON format. Due to the nature of JSON-RPC APIs using JSON formats, strictly use JSON only as described here. If you wish to use any other format than JSON, it should be converted outside of any OpenRPC tooling.
Introduction. This field guide will help developers on their OpenRPC journey to code automation and tooling. It is meant to be a starting place for new users and a resource for existing users. What is JSON-RPC? JSON-RPC is a light-weight remote procedure call (RPC) protocol.
