eth_sendRawTransactionHTTP

Submits a locally signed serialized transaction. Use the selected network's chain ID and supported transaction type. The in-docs sender does not broadcast transactions.

Chain EthereumTransport HTTPTry-it docs only

How to use

This method is documentation-only (broadcasts signed payloads / real funds).
Sign locally, then send from your own tooling with the example shape.

Parameters

JSON-RPC positional arguments — order matches the array sent in params. Index badges below match array positions.

signedTxDATArequired

Signed transaction bytes as hex DATA. Legacy transactions use RLP; typed transactions use a type byte followed by their encoded payload. Blob submissions must also use the sidecar format expected by the selected upstream. Never send a private key. The signed-bytes placeholder in the example is intentionally not executable.

params array (shape)

eth_sendRawTransaction · paramsjson

1[
2  "0x00"
3]

Try it

This method is documentation-only: it broadcasts a signed transaction and costs real funds, so the docs never send it for you. Use the example above from your own tooling.

Example request

eth_sendRawTransaction · requestbash

1curl 'https://ethras.org/v1/ethereum/<YOUR_KEY>' \
2  -H 'Content-Type: application/json' \
3  -d '{
4    "id": 1,
5    "jsonrpc": "2.0",
6    "method": "eth_sendRawTransaction",
7    "params": [
8      "0x02f8...signed-bytes..."
9    ]
10  }'

Example response

Illustrative example: long hex values and object fields may be shortened for readability. Available fields depend on the network, client, protocol upgrade and transaction type.

eth_sendRawTransaction · responsejson

1{
2  "jsonrpc": "2.0",
3  "id": 1,
4  "error": {
5    "code": -32000,
6    "message": "invalid sender"
7  }
8}

Response fields

The result row describes the complete result; other rows describe its object fields or array elements. Indented rows describe nested members. For subscriptions,params.* rows describe later notifications rather than the initial reply.

Field	Type	Description
`result`	`DATA(32B)`	Transaction hash when the serving upstream accepts the submission. This does not prove inclusion, execution success or finality; query the receipt.