API Reference
Solana RPC Proxy
Drop-in replacement for your Solana RPC URL. Use any Solana client library without code changes.
POST
/?api-key=YOUR_API_KEYOverview
BoltTx exposes a Solana JSON-RPC compatible endpoint so you can migrate from your existing RPC provider with a single URL change. The proxy accepts the sendTransaction method and forwards it through our optimized delivery infrastructure.
Why use RPC mode? If you're already using @solana/web3.js, solana-pyor solana-client (Rust), simply swap the RPC URL — no rewrite needed. For new integrations, we recommend the REST API for cleaner error handling.
Supported Methods
| Method | Status | Description |
|---|---|---|
| sendTransaction | Supported | Submit a signed transaction for delivery |
| Other methods | Not supported | Use your regular Solana RPC for queries |
For queries (getAccountInfo, getBalance, etc.), keep using your regular Solana RPC endpoint. BoltTx is focused on fast, reliable transaction delivery — not general-purpose RPC.
Usage Example
import { Connection } from "@solana/web3.js";
// Drop-in replacement — just swap your RPC URL
const connection = new Connection(
"https://bolttx.io/?api-key=YOUR_API_KEY",
"confirmed"
);
// Your existing sendRawTransaction code continues to work
const signature = await connection.sendRawTransaction(
signedTx.serialize(),
{ skipPreflight: true }
);
console.log("Signature:", signature);Response
Success
{
"jsonrpc": "2.0",
"id": 1,
"result": "5xKnR8qXeVm3pN..."
}Error
{
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": 403,
"message": "Invalid API key"
}
}Error Codes
| Code | Meaning |
|---|---|
| 401 | Missing API key |
| 402 | Transaction missing or insufficient tip |
| 403 | Invalid API key or unsupported method |
| 429 | Rate limit exceeded; the cap is per-user (shared across all your API keys) |
| -32602 | Invalid parameters (bad encoding or format) |
| -32603 | Internal error during delivery |