> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalasset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# DA Parties

> Explains the role of Digital Asset parties in Registry workflows.

## Operator Party

The DA operator party is used

* as a **signatory** on onboarding contracts (i.e. `ProviderService`)
* as an **observer** on all other Registry contracts (e.g. `InstrumentConfiguration`, `TransferPreapproval`, ...)

The latter is required for DA to be able to run the Registry Operator backend for explicit disclosure of the choice context.

Importantly, the DA operator party does not need to confirm any Registry transactions, with the exception of the initial onboarding transaction.

### How to retrieve it

Use the environment-specific operator endpoint:

<Tabs>
  <Tab title="MainNet">
    [https://api.utilities.digitalasset.com/api/utilities/v0/operator](https://api.utilities.digitalasset.com/api/utilities/v0/operator)
  </Tab>

  <Tab title="TestNet">
    [https://api.utilities.digitalasset-staging.com/api/utilities/v0/operator](https://api.utilities.digitalasset-staging.com/api/utilities/v0/operator)
  </Tab>

  <Tab title="DevNet">
    [https://api.utilities.digitalasset-dev.com/api/utilities/v0/operator](https://api.utilities.digitalasset-dev.com/api/utilities/v0/operator)
  </Tab>
</Tabs>

## Accounting Parties

DA accounting parties are DA-controlled beneficiary parties used to receive Digital Asset's contractual share of Traffic-Based App Rewards from featured providers and registrars.

### How to retrieve it

The correct accounting parties will be shared during the setup of a commercial agreement with Digital Asset. Please reach out to your DA contact for details.