QUICKTXN / DOCUMENTATION
API reference
The public interface accepts a single JSON-RPC request per POST. Use your chain RPC for general state queries.
Methods and paths
| Request | Authentication | Purpose |
|---|---|---|
| POST / · eth_chainId | Public | Chain discovery; empty params |
| POST / · eth_sendRawTransaction | X-Api-Key | One signed transaction hex in params |
| GET /tip-addresses | X-Api-Key | Account and chain-specific fee receivers |
GET /health is process liveness and GET /ready is readiness where exposed by your endpoint. Neither proves that a transaction will execute successfully. Internal metrics and relay interfaces are not customer APIs.
Request format
{"jsonrpc":"2.0","id":2,"method":"eth_sendRawTransaction","params":["0xSIGNED_TRANSACTION_HEX"]}Use Content-Type: application/json. Send one JSON object, not a JSON-RPC batch. The default application body limit is 65,536 bytes; deployment limits may be lower. A public eth_chainId request must fit within 512 bytes. Send a non-null request ID and parse each response rather than assuming IDs are preserved for every local error.
Use a replay-protected EVM transaction signed for the selected chain. EIP-1559 (type 0x02) is the recommended integration format for this launch; other envelopes and contract fee patterns require explicit compatibility validation with your account. Solana wire transactions and unsigned EVM objects are not accepted.
Response handling
A sequencer acceptance response contains a transaction hash in result. That is not an execution receipt. Inspect the JSON-RPC error object even on HTTP 200. Some upstream/transport failures use a non-JSON-RPC body, so check content and status before parsing.
| HTTP | Typical meaning | Action |
|---|---|---|
| 400 | Malformed payload, unsupported method, invalid transaction or chain mismatch | Fix the request; do not blind-retry |
| 401 | Missing, invalid, or revoked credential | Check assigned product and key; contact support if persistent |
| 402 | Fee admission rejected | Check account policy and current receiver discovery |
| 403 | Submission disabled or chain not granted | Confirm the entitlement and endpoint |
| 421 | Hostname is not assigned to this product | Use the exact assigned QuickTxn hostname |
| 413 | Payload exceeds configured cap | Reduce payload; no batch requests |
| 429 | Rate limit reached | Back off with jitter within your assigned allowance |
| 502 / 503 | Upstream, admission policy, stale credential cache, or readiness unavailable | Check receipt before bounded retry |
Responses may also come from the edge proxy, including an unknown-host rejection. Error text is diagnostic, not a stable parser contract. Use HTTP status and JSON-RPC fields together.
Rate limits
Your assigned limit controls throughput. Current key buckets are per edge process; they are not a global quota mechanism or a promise of multiplied capacity. Ask support to confirm your account allowance before spreading traffic across regions. Do not assume a default or unlimited submissions.