HTTP reference
SWQoS HTTP routes for raw transactions and bundles, health checks and tip floor snapshots
// updated 2026-11-17
Supanode issues keys through Telegram. Default minimum tip: 0.001 SOL; default rate: 15 sends/s per key per metro. Your key settings can differ. Declared tips are off by default and require enablement and a payment arrangement with Supanode. If your key returns partner_declared_tips, use an on-chain transfer instead.
Use the same hosts and ports as JSON-RPC. Authenticate with an API key, except for GET /health.
| Route | Request | Response |
|---|---|---|
POST /binary | Raw transaction bytes or a payload envelope | Transaction signature or bundle ID as plain text |
POST /plaintext | The same payload encoded as base64 text | Transaction signature or bundle ID as plain text |
GET /health | No body or API key | ok or unhealthy as plain text |
GET /tip_floor | No body | Array of zero or one tip floor snapshots |
POST to any other path | JSON-RPC request | JSON-RPC response |
| Any other method or path | Unsupported route | HTTP 404, reason invalid_request, problem not_found |
The payload envelope defines transaction, bundle and declared tip payloads. Raw sends have no preflight simulation. Each route reference defines its body limits, responses and examples.
Raw HTTP refusals return a JSON rejection object in the response body. A successful send acknowledges acceptance; check landing through your Solana RPC provider as described in Confirmation and retries.
OpenAPI
Import http.json for the raw submission routes, health.json for health or tip-floor.json for the tip floor. The last two documents also include their JSON-RPC methods.