Documentation/Canton Network Docs/Admin APIgRPC APIPackagescom.digitalasset.canton.admin.participant.v30ServicesParticipantRepairServiceView on Canton Network Docs ↗
ExportAcs
RPC
/com.digitalasset.canton.admin.participant.v30.ParticipantRepairService/ExportAcsProtocol Details
Inputs
ExportAcsRequest
party_idsrepeated stringsynchronizer_idstringledger_offsetint64contract_synchronizer_renamesrepeated mapexcluded_stakeholder_idsrepeated stringOutputs
ExportAcsResponse
chunkbytesRelated Schemas
com.digitalasset.canton.admin.participant.v30.ExportAcsRequest
com.digitalasset.canton.admin.participant.v30.ExportAcsRequest
party_idsrepeated stringsynchronizer_idstringledger_offsetint64contract_synchronizer_renamesrepeated mapexcluded_stakeholder_idsrepeated stringcom.digitalasset.canton.admin.participant.v30.ExportAcsResponse
com.digitalasset.canton.admin.participant.v30.ExportAcsResponse
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.ParticipantRepairService/ExportAcs <<'EOF'
{
"partyIds": [
"string"
],
"synchronizerId": "string",
"ledgerOffset": "0",
"contractSynchronizerRenames": [
{
"key": {
"targetSynchronizerId": "string"
}
}
],
"excludedStakeholderIds": [
"string"
]
}
EOF
OKapplication/json
OK
{
"chunk": "BASE64_ENCODED_BYTES"
}