Send a signed transaction
Authorizations
ApiKeyAuthApiKeyAuthapi-key string
NOWNodes API key passed in the api-key header.
Submits a signed, RLP-encoded transaction to the network and returns its hash.
The only write path on this endpoint. Our nodes hold no keys, so eth_sendTransaction and eth_signTransaction cannot be used - sign on your side and submit the raw bytes here.
Only replay-protected (EIP-155) transactions are accepted. Malformed input is rejected by the RLP decoder before it reaches the pool, e.g. -32000 rlp: value size exceeds available input length.
Changed in the 29 August 2026 network upgrade.
- Submission no longer fails after the transaction has been accepted. Previously, if sender recovery failed - which can happen at a fork activation boundary - the call returned an error even though the transaction was already in the pool, inviting a duplicate resend. It now returns the hash.
- Pre-EIP-155 (unprotected) transactions remain rejected with
only replay-protected (EIP-155) transactions allowed over RPC, with one hard-coded carve-out on mainnet: the canonical Arachnid deterministic-deployer transaction, pinned by exact hash. - EIP-7702 set-code transactions (
type 0x4) are accepted. EIP-4844 blob transactions (type 0x3) are still NOT supported and will be rejected.
Body
jsonrpcstringrequiredJSON-RPC version
methodstringrequiredMethod name
paramsArray<string>requiredArray containing a single signed transaction data (hex string)
idintegerrequiredRequest ID
Response
Transaction successfully sent
Method not served by this endpoint. The body is the plain-text string
Method Not Allowed, not JSON.
Missing API key - the api-key header was absent. The body is the
plain-text string Missing API_key, not JSON.