CompletionStream

Ledger API›gRPC API›v2›CompletionStream

com.daml.ledger.api.v2

CompletionStream

gRPCSince 3.4.4

RPC/com.daml.ledger.api.v2.CommandCompletionService/CompletionStream

Protocol Details

Inputs

CompletionStreamRequest

user_idstring

partiesrepeated string

begin_exclusiveint64

Outputs

CompletionStreamResponse

completionCompletion

offset_checkpointOffsetCheckpoint

Lifecycle Changes

3.4.4introduced

Related Schemas

com.daml.ledger.api.v2.CompletionStreamRequest

user_idstring

partiesrepeated string

begin_exclusiveint64

com.daml.ledger.api.v2.CompletionStreamResponse

completionCompletion

offset_checkpointOffsetCheckpoint

com.daml.ledger.api.v2.Completion

command_idstring

statusStatus

update_idstring

user_idstring

act_asrepeated string

submission_idstring

deduplication_offsetint64

deduplication_durationDuration

trace_contextTraceContext

offsetint64

synchronizer_timeSynchronizerTime

paid_traffic_costint64

com.daml.ledger.api.v2.TraceContext

traceparentstring

tracestatestring

com.daml.ledger.api.v2.SynchronizerTime

synchronizer_idstring

record_timeTimestamp

com.daml.ledger.api.v2.OffsetCheckpoint

offsetint64

synchronizer_timesrepeated SynchronizerTime

grpcurl

grpcurl

# Add -plaintext if the server is not using TLS.
# This RPC uses streaming semantics. Send additional JSON messages on stdin as needed.
grpcurl \
  -d @ \
  <HOST:PORT> \
  com.daml.ledger.api.v2.CommandCompletionService/CompletionStream <<'EOF'
{
  "userId": "string",
  "parties": [
    "string"
  ],
  "beginExclusive": "0"
}
EOF

OKapplication/json

OK

{
  "completion": {
    "commandId": "string",
    "status": "string",
    "updateId": "string",
    "userId": "string",
    "actAs": [
      "string"
    ],
    "submissionId": "string",
    "deduplicationOffset": "0"
  }
}