[Transaction] klay_call
Executes a new message call immediately without creating a transaction on the block chain. It returns data or an error object of JSON RPC if error occurs.
If you deployed a contract, use klay_getTransactionReceipt to get the contract address.
NOTE In versions earlier than Kaia v1.7.0, only integer block number, the string "earliest" and "latest" are available.
JSONRPC: klay_call
Request
- application/json
Body
Array [
- CallObject
]
params
object[]
required
anyOf
The transaction call object. See the next table for the object's properties.
(optional) The address the transaction is sent from.
(optional when testing the deployment of a new contract) The address the transaction is directed to.
(optional) Integer of the gas provided for the transaction execution. klay_call consumes zero gas, but this parameter may be needed by some executions.
(optional) Integer of the gasPrice used for each paid gas.
(optional) Integer of the value sent with this transaction.
(optional) Hash of the method signature and encoded parameters. It replaces data field, but 'data` field is still supported for backward compatibility.
Responses
- 200
Return value of executed contract or returns an error object of JSON RPC if anything goes wrong
- application/json
- Schema
- Example (from schema)
Schema
error
object
A Number that indicates the error type that occurred. This MUST be an integer.
code | message | description |
---|---|---|
-32700 | Parse error | invalid JSON was received by the server. An error occurred on the server while parsing the JSON text. |
-32602 | Invalid params | Invalid method parameter(s). |
A String providing a short description of the error. The message SHOULD be limited to a concise single sentence.
A Primitive or Structured value that contains additional information about the error. This may be omitted. The value of this member is defined by the Server (e.g. detailed error information, nested errors etc.).
The return value of executed contract.
{
"jsonrpc": "2.0",
"id": 0,
"error": {
"code": -32700,
"message": "Parse error",
"data": "string"
},
"result": "0x000000000000000000000000000000000000000000000000000000000000000a"
}