Documentation/Canton Network Docs/Admin APIgRPC APIPackagescom.digitalasset.canton.admin.participant.v30ServicesPartyManagementServiceView on Canton Network Docs ↗
ExportPartyAcs
RPC
/com.digitalasset.canton.admin.participant.v30.PartyManagementService/ExportPartyAcsProtocol Details
Inputs
ExportPartyAcsRequest
party_idstringsynchronizer_idstringtarget_participant_uidstringbegin_offset_exclusiveint64wait_for_activation_timeoutDurationOutputs
ExportPartyAcsResponse
chunkbytesRelated Schemas
com.digitalasset.canton.admin.participant.v30.ExportPartyAcsRequest
com.digitalasset.canton.admin.participant.v30.ExportPartyAcsRequest
party_idstringsynchronizer_idstringtarget_participant_uidstringbegin_offset_exclusiveint64wait_for_activation_timeoutDurationcom.digitalasset.canton.admin.participant.v30.ExportPartyAcsResponse
com.digitalasset.canton.admin.participant.v30.ExportPartyAcsResponse
chunkbytesgrpcurl
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.digitalasset.canton.admin.participant.v30.PartyManagementService/ExportPartyAcs <<'EOF'
{
"partyId": "string",
"synchronizerId": "string",
"targetParticipantUid": "string",
"beginOffsetExclusive": "0",
"waitForActivationTimeout": "string"
}
EOF
OKapplication/json
OK
{
"chunk": "BASE64_ENCODED_BYTES"
}