Similar to ExecuteSubmission but _synchronously_ wait for the completion of the transaction

POST /v2/interactive-submission/executeAndWait

Request

curl --request POST \
  --url 'http://localhost:7575/v2/interactive-submission/executeAndWait' \
  --header 'Authorization: Bearer $TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{"preparedTransaction":"string","partySignatures":{"signatures":[{}]},"deduplicationPeriod":{},"submissionId":"string","userId":"string","hashingSchemeVersion":"HASHING_SCHEME_VERSION_UNSPECIFIED","minLedgerTime":{"time":{}}}'

200 response

{
  "updateId": "string",
  "completionOffset": 0
}

JSON Ledger API

Similar to ExecuteSubmission but synchronously wait for the completion of the transaction

OpenAPISince 3.4Changed 3.5

Similar to ExecuteSubmission but synchronously wait for the completion of the transaction

Protocol Details

Operation IDpostV2Interactive-submissionExecuteandwait

AuthenticationBearer token

Published3.5

Inputs

Request body

application/json

preparedTransaction · string · required

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

partySignatures · object · required

OpenAPI type: PartySignatures.

Additional signatures provided by the submitting parties

deduplicationPeriod · object

OpenAPI type: DeduplicationPeriod2.

submissionId · string · 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

userId · string

See [PrepareSubmissionRequest.user_id] Optional

hashingSchemeVersion · string · required

The hashing scheme version used when building the hash Required

minLedgerTime · object

OpenAPI type: MinLedgerTime.

Outputs

200

application/json

updateId · string · required

The id of the transaction that resulted from the submitted command. Must be a valid LedgerString (as described in value.proto). Required

completionOffset · integer (int64) · required

The details of the offset field are described in community/ledger-api/README.md. Required

400

text/plain

value · string · required

default

application/json

code · string · required

cause · string · required

correlationId · string

traceId · string

context · Map_String · required

resources · Tuple2_String_String[]

errorCategory · integer (int32) · required

grpcCodeValue · integer (int32)

retryInfo · string

definiteAnswer · boolean

History

Changed3.5

The POST /v2/interactive-submission/executeAndWait operation changed in this snapshot.

Introduced3.4

Request

curl --request POST \
  --url 'http://localhost:7575/v2/interactive-submission/executeAndWait' \
  --header 'Authorization: Bearer $TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{"preparedTransaction":"string","partySignatures":{"signatures":[{}]},"deduplicationPeriod":{},"submissionId":"string","userId":"string","hashingSchemeVersion":"HASHING_SCHEME_VERSION_UNSPECIFIED","minLedgerTime":{"time":{}}}'

200 response

{
  "updateId": "string",
  "completionOffset": 0
}