RPC
Use RPC for individual reads, transaction history, and signed transaction submission. Requests use Solana's JSON-RPC interface over HTTPS.
Connect
New York uses https://rpc.ny.shreds.xyz. Find Frankfurt and Amsterdam in the endpoint directory. Append your service's access key as ?api-key=YOUR_SERVICE_ACCESS_KEY, as described in authentication.
curl --silent --show-error "https://rpc.ny.shreds.xyz/?api-key=$SHREDS_API_KEY" \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"getSlot","params":[{"commitment":"confirmed"}]}'
Requests contain jsonrpc: "2.0", an id, a method, and method-specific params. Match responses by id and inspect the error field even when HTTP succeeds.
Common operations
| Task | Methods |
|---|---|
| Account state | getAccountInfo, getMultipleAccounts, getBalance |
| Token holdings | getTokenAccountBalance, getTokenAccountsByOwner |
| Chain progress | getSlot, getBlockHeight, getLatestBlockhash |
| History | getBlock, getTransaction, getSignaturesForAddress |
| Transaction preparation and submission | simulateTransaction, sendTransaction |
| Confirmation | getSignatureStatuses |
Method availability, request limits, and retained history depend on your service. Do not assume every historical block is available.
Commitment
Choose processed for the node's earliest processed view, confirmed for a stronger confirmation signal, or finalized for workflows requiring finality. Lower commitment may expose data from forks that do not survive. Set commitment explicitly where supported.
Sending and SWQoS
Use regular RPC for standard submission or your regional SWQoS endpoint for stake-weighted transaction delivery where enabled. SWQoS does not guarantee inclusion or replace priority fees. See sending transactions.
Production use
Set timeouts, bound concurrency, and back off on rate limits. Retry transient read failures with capped delays. A transaction submission timeout leaves the outcome unknown; check its signature before replacing it.