π¨βπΌ Send transaction from node-managed account
Code samples
POST /api/v1/eth/account/send
curl -X POST 'https://settla.net/api/v1/eth/account/send' \
-H 'X-API-Key: $SETTLA_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"transaction": {
"from": "0x535cac072a2dc4ccc9d810e8a376d8f3c09dd615",
"to": "0x6928f3e126dbac9923d52300fdef714b280b305c",
"value": "0xdd09beac4d71c",
"gas": "0x5208"
}
}'
Sends a transaction using eth_sendTransaction. The from account must be unlocked on the ETH node.
Not usable on the production node. Erigon holds no keys and does not implement eth_sendTransaction, so this endpoint answers 500 on the live API. Sign on your side and submit through POST /api/v1/eth/transactions/send-raw instead β that is the supported path and the one the SDKs use.
Body parameter
{
"transaction": {
"from": "0x535cac072a2dc4ccc9d810e8a376d8f3c09dd615",
"to": "0x6928f3e126dbac9923d52300fdef714b280b305c",
"value": "0xdd09beac4d71c",
"gas": "0x5208"
}
}
π οΈ Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| body | body | object | true | none |
| Β» transaction | body | object | true | Ethereum transaction parameters used with eth_call, eth_estimateGas and eth_sendTransaction. |
| »» from | body | string | false | Sender address. |
| »» to | body | string¦null | false | Recipient address, or null for contract creation. |
| »» gas | body | string | false | Gas limit as hex QUANTITY. |
| »» gasPrice | body | string | false | Legacy gas price as hex QUANTITY. |
| »» maxFeePerGas | body | string | false | EIP-1559 max fee per gas as hex QUANTITY. |
| »» maxPriorityFeePerGas | body | string | false | EIP-1559 priority fee per gas as hex QUANTITY. |
| »» value | body | string | false | Amount of wei to send as hex QUANTITY. |
| »» data | body | string | false | Call data or contract deployment bytecode. |
| »» nonce | body | string | false | Nonce as hex QUANTITY. |
Example responses
200 Response
{
"transactionHash": "0x034f561a3af0d2ea225dee1f9539fdb5c77769b85cecadf1bfda9bea8e178f01"
}
422 Response
{
"error": "Field \"transaction\" is required and must be an object"
}
500 Response
{
"error": "Could not connect to ETH node."
}
π Responses
| Status | Meaning | Description | Schema |
|---|---|---|---|
| 200 | OK | Transaction accepted by node | Inline |
| 422 | Unprocessable Entity | Invalid request body (missing or invalid transaction) | Inline |
| 500 | Internal Server Error | Node has no unlocked accounts or is unreachable. This is the response returned by the production node. | Inline |
π Response Schema
Status Code 200
| Name | Type | Required | Restrictions | Description |
|---|---|---|---|---|
| Β» transactionHash | string | false | none | Transaction hash returned by eth_sendTransaction. |
Status Code 422
| Name | Type | Required | Restrictions | Description |
|---|---|---|---|---|
| Β» error | string | false | none | none |
Status Code 500
| Name | Type | Required | Restrictions | Description |
|---|---|---|---|---|
| Β» error | string | false | none | none |