Each node has dedicated computing resources that are only accessible using your API key. Your node subscription also has its own DNS host name associated with it. All API and middleware requests to your nodes will include the node's host name in order to route traffic to the correct blockchain node.
Each node is assigned a host name generated by the DEPLOY infrastructure. This host name is unique to each node subscription and cannot be changed. Generally, host names follow the structure
<node name>.nodes.deploy.radar.tech, where
<node name> is the unique host name assigned to your node.
This fully qualified host name can be resolved by any public DNS server on the Internet and will serve as the base for any API URIs for both the blockchain node itself or any installed middleware. For example, a Geth node on the Ethereum mainnet may have a host name similar to
gethmainnet12345.nodes.deploy.radar.tech, the JSON-RPC URI for querying the Ethereum node would be
https://gethmainnet12345.nodes.deploy.radar.tech/, and if GraphQL middleware were installed it would be available at the URI
All nodes use API keys as an authentication layer in order to ensure that only the node's owner has the ability to perform queries and send requests to that node. These API keys should be kept secret and should be provided with each API request.
Your node API keys must be added as a GET argument when performing any HTTP requests (including JSON-RPC) to either your node's blockchain interfaces or its installed middleware. The API parameter will be named
apikey. For example the full URI and the API key parameter for a Bitcoin node's JSON-RPC interface would be
https://rpcuser:firstname.lastname@example.org/?apikey=aaaabbbbccccddddeeeeffff which includes the API key to access the node.
Your owned node's specific connection information is available from anywhere within the node detail view of the DEPLOY application. Simply navigate to your owned node from the DEPLOY application's node list and click Connect to Node in the upper right-hand corner of the screen to view your detailed connection information. This will include the URI for making JSON-RPC requests to your owned node as well as SSH connection information.
Bitcoin nodes include the HTTP basic authentication portion of the HTTP URI (
rpcuser:rpcpass@ must be included in all HTTP JSON-RPC requests.
Nodes also offer the ability to create a Secure Shell (SSH) connection to your node in order to install custom applications or to run custom scripts. The SSH connection information is also found by clicking the Connect to Node button on the node detail view within the DEPLOY application.