API keys
Request and manage your Supanode SWQoS API key through Telegram; HTTP and QUIC authentication.
// updated 2026-11-17
Request and manage your key
Contact Supanode on Telegram. We issue your SWQoS key and confirm its minimum tip, send rate and enabled features. Request additional keys, rotation, pause, resumption or revocation through the same channel. You do not need a partner console account. Store the secret securely; do not expose it in browser code, repositories or support logs.
The default minimum tip is 1,000,000 lamports (0.001 SOL) and the default rate is 15 sends per second per key per metro. Your issued key can have different settings. SWQoS keys are separate from read RPC credentials. Support manages any account-management credentials; they are not used for transaction submissions.
Access and billing
SWQoS tips are paid in SOL. There is no subscription or per-send fee. The default minimum on-chain tip is 0.001 SOL; the tip transfers only if execution succeeds. Network fees are separate.
Declared tips are off by default. Request enablement and agree payment with Supanode before using them. A declaration is billed under that arrangement; it is separate from an on-chain transfer and from other product subscriptions. An overdue declared-tip payment can suspend submissions while queries remain available. Adding an on-chain transfer does not bypass a payment suspension. See declared-tip billing and retry rules.
Supanode handles keys, enabled features and payment questions through Telegram. Ask for the applicable service terms there. Do not create or send account-management credentials to a transaction endpoint.
HTTP
Send the key in the x-api-key header. This keeps it out of request URLs.
The authentication reference covers compatibility
forms and their precedence.
Set SWQOS_API_KEY to your key. These examples call getHealth to check the connection without submitting a transaction. Rust and Go use the
example project; TypeScript uses fetch.
use serde_json::{Value, json};
use swqos_examples::swqos::{Result, required};
#[tokio::main]
async fn main() -> Result<()> {
let response = reqwest::Client::new()
.post("https://fra.tpu.supanode.xyz")
.header("x-api-key", required("SWQOS_API_KEY")?)
.json(&json!({ "jsonrpc": "2.0", "id": 1, "method": "getHealth" }))
.send()
.await?;
let status = response.status();
let body = response.text().await?;
let reply: Value = serde_json::from_str(&body)
.map_err(|error| format!("HTTP {status}: {error}; body: {body}"))?;
if !status.is_success() || reply.get("error").is_some_and(|error| !error.is_null()) {
return Err(format!("HTTP {status}: {reply}").into());
}
println!("{}", serde_json::to_string_pretty(&reply)?);
Ok(())
}
All HTTP routes need a key except GET /health. Use HTTPS. Hosted endpoints do not
provide CORS headers. See the HTTP route reference.
QUIC
Put the key in the client certificate's first common name (CN). A self signed
certificate works. Follow the QUIC connection setup for
ALPN and server certificate verification.
Declared tips and refusals
Using a key does not enable declared tips. Ask for declared tip access and payment through Supanode on Telegram first.
A missing, unknown or revoked key returns
unauthorized. Support can pause a key while it
investigates; a paused key returns key_paused until
it's resumed. An overdue declared tip payment returns
payment_required on submissions; queries remain
available. Resolve payment through your agreed billing setup or
ask for help on Supanode on Telegram.