Initiate adding a party already hosted on one or more source participants to this target participant in the specified synchronizer. Performs some checks synchronously and then starts the party addition asynchronously.

Depends on the party authorizing the PartyToParticipant topology proposal at the specified topology_serial prior or concurrently to this endpoint. On the other hand, this target participant authorizes the topology proposal as part of this endpoint in a specific, intermediate step, and therefore the target participant signature must not already be in place prior to the call.

Export the ACS for the given parties from the participant.

Export the ACS for the given parties at a timestamp (that is the effective time of a topology transaction).

Status endpoint that given an add_party_request_id returns status information about progress, completion, or errors of a previous call to AddPartyAsync on the source or target participant.

Note that the status reflects the state as perceived by this participant and does not imply the state of other participants. The status on the target participant is more authoritative as the target participant drives the process of adding the party. For example when the target participant status indicates "completed", the party has been added successfully.

For a given timestamp, find the highest ledger offset among all events that have record time <= timestamp.

Returns a ledger offset, or an error otherwise. Depending on the error cause, a retry may make sense. Retryable errors are defined as: OUT_OF_RANGE/INVALID_TIMESTAMP_PARTY_MANAGEMENT_ERROR. Further, a returned offset is guaranteed to be "clean", meaning all events have been processed fully and published to the Ledger API DB until the requested timestamp.