Introduction

Most blockchain daemons support JSON-RPC as their primary method of out-of-the-box API access for connections from other applications. This HTTP-based remote procedure call specification allows clients to execute functions, pass parameters, and receive results from system calls within the chain daemon.

Primarily used for interacting with wallets, chain data, and transactions - JSON-RPC APIs can also information about the current state of mempools, estimate the fees for sending a transaction on a given network, or to verify message signatures.

All DEPLOY-supported blockchains use JSON-RPC as their primary API interface and will be the default for the HTTP endpoint for your owned node or shared node subscription.

Usage

JSON-RPC APIs are avaialable via HTTP connections to the blockchain daemon on all DEPLOY owned node and shared node subscriptions. Your node’s JSON-RPC API endpoint is available by clicking Connect to Node in your node detail view. Simply use this API endpoint in your JSON-RPC-capable client to access your chain daemon.

A shared Ethereum node’s Connect To Node modal

Authentication

Your owned node or shared node subscription will require the use of an API Key to authenticate your request against your subscription. Simply include the apikey GET parameter with your API in your JSON-RPC requests as illustrated in your node’s Connect to Node modal example.

Bitcoin

Bitcoin chain daemons require the inclusion of JSON-RPC usernames and passwords as indicated in the Connect to Node modal example for your Bitcoin owned node or shared node subscription. These take the form of https://rpcuser:rpcpass@bitcoin... in the cURL example.

A Bitcoin shared node’s Connect to Node modal