Sandbox version
For experimental use only. Proceed with caution.
Transaction Methods
Submit a multi-signed transaction
wss://honeycluster.io
rpc method: submit_multisigned

Submits a multi-signed transaction. The transaction JSON must include a Signers array with all required signatures.

Try it now
Response · submit_multisigned WS Response
{
  "result": {
    "engine_result": "tesSUCCESS",
    "engine_result_code": 0,
    "engine_result_message": "The transaction was applied. Only final in a validated ledger.",
    "tx_json": {
      "Account": "rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn",
      "TransactionType": "Payment",
      "hash": "E08D6E9754025BA2534A78707605E0601F03ACE063687A0CA1BDDACFCD1698C7"
    }
  },
  "status": "success",
  "type": "response",
  "id": 1
}
Request Message
submit_multisigned WS Request
application/json
Submit a multi-signed transaction
FieldTypeDescription
command
required
string
WebSocket command name
id
object
Client-supplied identifier to correlate requests with responses.
tx_json
object
The transaction object with Signers array containing multiple signatures.
fail_hard
boolean
If true, do not retry or relay to other servers if the transaction fails locally.
api_version
object
API version for the response format. Version 2 is the default for rippled 2.0+.
Example
Json
{
  "command": "submit_multisigned",
  "id": 1,
  "tx_json": {
    "Account": "rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn",
    "TransactionType": "Payment",
    "Destination": "rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe",
    "Amount": "1000000",
    "Fee": "120",
    "Sequence": 42,
    "Signers": [
      {
        "Signer": {
          "Account": "rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe",
          "SigningPubKey": "023693F15967AE357D0327974AD46FE3C127113B1110D6044520CC26B62CF1AD16",
          "TxnSignature": "304402..."
        }
      }
    ]
  }
}
Response Message
submit_multisigned WS Response
application/json
WebSocket response for submit_multisigned
FieldTypeDescription
result
object
status
enum<string>
Available
successerror
type
string
id
stringnumber
Echo of the client-provided correlation ID
Example
Json
{
  "result": {
    "engine_result": "tesSUCCESS",
    "engine_result_code": 0,
    "engine_result_message": "The transaction was applied. Only final in a validated ledger.",
    "tx_json": {
      "Account": "rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn",
      "TransactionType": "Payment",
      "hash": "E08D6E9754025BA2534A78707605E0601F03ACE063687A0CA1BDDACFCD1698C7"
    }
  },
  "status": "success",
  "type": "response",
  "id": 1
}