HTTP Transaction Submission
HTTP/HTTPS transaction submission methods
Raiden supports two HTTP submission methods. Both use the api-x-token header for authentication and return a transaction signature in the response.
| Method | Format | Best For |
|---|---|---|
| sendTransaction | JSON-RPC + base64 | Standard integrations, compatibility |
| sendRawTransaction | Raw binary bytes | Lower overhead, faster path |
Common Configuration
| Property | Value |
|---|---|
| Transport | HTTP or HTTPS (TCP) |
| Ports | 443 (HTTPS) / 80 (HTTP) |
| Auth | api-x-token header |
| Response | Synchronous — returns transaction signature |
Use sendRawTransaction for new integrations — it skips JSON-RPC parsing and base64 decoding, sending your bytes straight into the routing pipeline.
Last updated on