For the complete documentation index, see llms.txt. This page is also available as Markdown.

submit

Submits a signed, serialized transaction to the network to be confirmed and included in future ledgers. Only submit-only mode (a signed tx_blob) is available through this endpoint; sign-and-submit mode, which requires the server to hold your secret, is not.

This method will use 80 Compute Units.


Reference: Here

Parameters

  • tx_blob (string, required) Hex representation of the signed transaction to submit. This can be a multi-signed transaction.

  • fail_hard (boolean, optional) If true, and the transaction fails locally, do not retry or relay the transaction to other servers. The default is false.

Returns

  • engine_result (string) Text result code indicating the preliminary result of the transaction, for example tesSUCCESS.

  • engine_result_code (integer) Numeric version of the result code.

  • engine_result_message (string) Human-readable explanation of the transaction's preliminary result.

  • tx_blob (string) The complete transaction in hex string format.

  • tx_json (object) The complete transaction in JSON format.

  • accepted (boolean) true if the transaction was applied, queued, broadcast, or kept for later.

  • account_sequence_available (number) The next Sequence Number available for the sending account after all pending and queued transactions.

  • account_sequence_next (number) The next Sequence Number for the sending account after all provisionally applied transactions.

  • applied (boolean) true if this transaction was applied to the open ledger.

  • broadcast (boolean) true if this transaction was broadcast to peer servers.

  • kept (boolean) true if the transaction was kept to be retried later.

  • queued (boolean) true if the transaction was put in the transaction queue.

  • open_ledger_cost (string) The current open ledger cost before processing this transaction.

  • validated_ledger_index (integer) The ledger index of the newest validated ledger at the time of submission.

Over WebSocket, send {"id":1,"command":"submit","tx_blob":"1200002280000000240000000361D4838D7EA4C6800000000000000000000000000055534400000000004B4E9C06F24296074F7BC48F92A97916C6DC5EA968400000000000000A732103AB40A0490F9B7ED8DF29D246BF2D6269820A0EE7742ACDD457BEA7C7D0931EDB74473045022100D184EB4AE5956FF600E7536EE459345C7BBCF097A84CC61A93B9AF7197EDB98702201CEA8009B7BEEBAA2AACC0359B41C427C1C5B550A4CA4B80CF2174AF2D6D5DCE81144B4E9C06F24296074F7BC48F92A97916C6DC5EA983143E9D4A2B8AA0780F682D136F7A56D6724EF53754"} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.

A tesSUCCESS engine result is preliminary. Monitor the transaction with tx until it appears in a validated ledger before treating it as final.

Last updated

Was this helpful?