POST /v2/interactive-submission/execute

Execute a prepared submission asynchronously on the ledger. Requires actAs or executeAs scope for the submitting party when LAPI User authorization is enabled Requires a signature of the transaction from the submitting external party.

post/v2/interactive-submission/execute

Request body

preparedTransactionstring required

the prepared transaction Typically this is the value of the prepared_transaction field in PrepareSubmissionResponse obtained from calling prepareSubmission.

Required

submissionIdstring required

A unique identifier to distinguish completions for different submissions with the same change ID. Typically a random UUID. Applications are expected to use a different UUID for each retry of a submission with the same change ID. Must be a valid LedgerString (as described in value.proto).

Required

userIdstring

See [PrepareSubmissionRequest.user_id]

Optional

hashingSchemeVersion'HASHING_SCHEME_VERSION_UNSPECIFIED' | 'HASHING_SCHEME_VERSION_V2' | 'HASHING_SCHEME_VERSION_V3' required

The hashing scheme version used when building the hash

Required

Response

ExecuteSubmissionResponse required

Changes

No recorded changes to this endpoint across all 1 revision of this API.