Documentation/canton-network-docs/Admin APIgRPC APIPackagescom.digitalasset.canton.admin.participant.v30ServicesPartyManagementServiceView on canton-network-docs ↗
canton-network-docs/Admin APIgRPC APIPackagescom.digitalasset.canton.admin.participant.v30ServicesPartyManagementService

GetHighestOffsetByTimestamp

Participant Administration›Protobuf›com.digitalasset.canton.admin.participant.v30›GetHighestOffsetByTimestamp

com.digitalasset.canton.admin.participant.v30

​
GetHighestOffsetByTimestamp

gRPCSince 3.4.0
RPC/com.digitalasset.canton.admin.participant.v30.PartyManagementService/GetHighestOffsetByTimestamp

​
Protocol Details

​
Inputs

​
GetHighestOffsetByTimestampRequest

synchronizer_idstring
timestampTimestamp
forcebool

​
Outputs

​
GetHighestOffsetByTimestampResponse

ledger_offsetint64

​
Lifecycle Changes

3.4.0introduced

com.digitalasset.canton.admin.participant.v30.GetHighestOffsetByTimestampRequest

synchronizer_idstring
timestampTimestamp
forcebool

com.digitalasset.canton.admin.participant.v30.GetHighestOffsetByTimestampResponse

ledger_offsetint64
grpcurl
grpcurl
# Add -plaintext if the server is not using TLS.
grpcurl \
  -d @ \
  <HOST:PORT> \
  com.digitalasset.canton.admin.participant.v30.PartyManagementService/GetHighestOffsetByTimestamp <<'EOF'
{
  "synchronizerId": "string",
  "timestamp": "string",
  "force": true
}
EOF
OKapplication/json
OK
{
  "ledgerOffset": "0"
}