Solana JSON-RPC
The full Solana JSON-RPC surface on
POST https://triport.io/sol— standard chain methods proxied verbatim, plus Triport extensions: DAS asset queries, priority-fee estimates, and bundle submission.
Choosing an endpoint or a plan rather than a method? See Solana RPC endpoint. Chain ID, RPC URL and network config: Solana chain ID & RPC URL.
- Method / Endpoint
POST https://triport.io/sol(all methods) ·POST https://fra.triport.io/sol— direct endpoint for sending transactions, see sendTransaction- Network
- Solana
- Authentication
x-tokenheader (recommended); see Authentication- Required scope
- — (tier-gated per method)
- Tier / rate limit
- Any tier; see Rate Limits
How to call
Every method takes the same envelope — only method and params change:
curl https://triport.io/sol \
-H "x-token: $TRIPORT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"getSlot","params":[]}'Batching (a JSON array of request objects) is supported; each entry is tier-checked and rate-limited individually.
Support semantics
Each method page carries a Type field:
| Type | Meaning |
|---|---|
| Native upstream RPC | Standard Solana RPC (getBalance, getSlot, …) — routed to an upstream node, result returned unchanged. |
| Triport extension | Not part of base Solana RPC — DAS (getAsset*, searchAssets, getTokenAccounts), getPriorityFeeEstimate, sendBundle, simulateBundle. |
Calling a method outside this catalog returns JSON-RPC -32601
(method_unknown) — see Errors.
Method reference
The pages below are grouped by what they do — accounts, blocks, transactions,
tokens, DAS assets, and network state. Subscription (*Subscribe) methods live
on the WebSocket channel — see Solana Pub/Sub WS.