The Nolimitnodes API provides four communication protocols for interacting with the Solana blockchain:

​
Endpoints

ProtocolEndpointUse Case
JSON-RPChttps://rpc.nln.clr3.orgQuerying blockchain state, sending transactions
WebSocket (RPC)wss://ws.nln.clr3.orgReal-time subscriptions (accounts, slots, logs)
Yellowstone gRPCgrpc.nln.clr3.org:443High-performance Geyser streaming (accounts, transactions, slots)
Data Streams (gRPC)stream-1.nln.clr3.org:443Jupiter swaps, Pump Fun, liquidity pools, token creations, wallet transfers
All endpoints authenticate via the x-api-key request header.

​
JSON-RPC Request Format

All RPC requests follow the JSON-RPC 2.0 specification:
​
jsonrpc
string
required
Must be "2.0".
​
id
integer
required
A unique identifier for the request.
​
method
string
required
The RPC method name (e.g., "getSlot", "getBalance").
​
params
array
Method-specific parameters.

​
Example Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getBalance",
  "params": ["83astBRguLMdt2h5U1Tbd1hZemEfWp1YGt6jZvoRoKCo"]
}

​
Example Response

{
  "jsonrpc": "2.0",
  "result": {
    "context": {
      "slot": 1
    },
    "value": 0
  },
  "id": 1
}

​
Data Stream Request Format

Data streams use gRPC server-streaming over HTTP/2. Send a SubscribeRequest proto message — the server responds with a continuous stream of SubscribeResponse messages until you close the connection.
​
topic
string
required
The topic name to subscribe to (e.g., "pumpFunTrades", "walletTransfers"). Use ListTopics to retrieve all available topics on your plan.
​
format
integer
required
Output format: 0 for Protocol Buffers binary, 1 for JSON. Use 1 (JSON) to receive the payload as a UTF-8 JSON string.

​
Example — Subscribe (grpcurl)

grpcurl \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"topic": "walletTransfers", "format": 1}' \
  stream-1.nln.clr3.org:443 \
  nln.stream.v1.StreamService/Subscribe

​
Example — List Topics (grpcurl)

grpcurl \
  -H "x-api-key: YOUR_API_KEY" \
  stream-1.nln.clr3.org:443 \
  nln.stream.v1.StreamService/ListTopics

​
Unsubscribing

Close the gRPC stream (disconnect). There is no unsubscribe message.

​
Commitment Levels

Many RPC methods accept an optional commitment parameter:
LevelDescription
finalizedBlock confirmed by supermajority of the cluster. Most reliable.
confirmedBlock has received votes from supermajority. Fast and reliable.
processedBlock processed by the connected node. Fastest but may be reverted.

​
Encoding Formats

Response data can be returned in different encodings:
FormatDescription
base58Base-58 encoded string (default for small data)
base64Base-64 encoded string
base64+zstdZstandard-compressed base-64 string
jsonParsedParsed JSON format (when available)