Preview a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state.
For V2 transactions (and beyond) the /preview-v2
endpoint should be used instead.
This endpoint is effectively a proxy towards the Core API /transaction/preview
endpoint. See the Core API documentation for more details.
A set of flags to configure the response of the transaction preview.
A text-representation of a transaction manifest
An array of hex-encoded blob data, if referenced by the manifest.
An integer between 0
and 10^10
, marking the epoch at which the transaction startsbeing valid.
If omitted, the current epoch will be used.
An integer between 0
and 10^10
, marking the epoch at which the transaction is no
longer valid. If omitted, a maximum epoch (relative to the start_epoch_inclusive
) will be used.
The notary public key to use. If not provided, this defaults to a fixed public key.
Whether the notary should be used as a signer (optional). If not provided, this defaults to false.
An integer between 0
and 65535
, giving the validator tip as a percentage amount.
A value of 1
corresponds to a 1% fee.
If not provided, this defaults to 0.
An integer between 0
and 2^32 - 1
, chosen to allow a unique intent to be created
(to enable submitting an otherwise identical/duplicate intent).
If not provided, this defaults to 0.
A list of public keys to be used as transaction signers. If not provided, this defaults to an empty array.
An optional transaction message. Only affects the costing.
This type is defined in the Core API as TransactionMessage
. See the Core API documentation for more details.