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

# Manage Masters

> Provision or register Master accounts and keep trading and fee balances separate.

A Master operates the strategy and represents the aggregate operating capital of its active Investors. Every Master requires a separate payment account for performance fee credits.

## Choose the correct path

| Scenario | Endpoint | Guidance |
| - | - | - |
| New integration | `POST /api/v1/master/create` | Recommended. Creates the trading and payment accounts together. |
| Coordinated migration | `POST /api/v1/master/add` | Registers two distinct MT5 accounts that already exist. |
| Catalog synchronization | `GET /api/v1/master/directory` | Always send `engine=PAMM` for this integration. |
| Read or update one Master | `GET/PATCH /api/v1/master/{master_id}` | Use the internal `id`, not `mt5_login`. |

## New Master provisioning

`/master/create` returns the Master login, payment account login, and MT5 credentials. Store the two accounts as distinct entities and restrict password access to authorized backend processes.

Always include `default_perf_fee`, expressed as a fraction from `0` to `1`:

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "default_perf_fee": "0.30"
}
```

This fragment configures a 30% default; the complete creation request and field definitions are in [Master endpoints](https://pamm-api.exuratech.com/reference/masters.md#create-a-new-master). Older deployments accept omission and use zero, whereas strict deployments require the field.

> [!NOTE]
>
> The payment account group is configured by ExuraCopy. The CRM supplies the agreed `platform_group` only for the Master trading account.

## Existing account registration

Before calling `/master/add`, confirm that:

* both MT5 accounts already exist on the assigned server;
* the payment account is different from the trading account;
* the payment account is not assigned to another Master;
* neither account is being used for the other's purpose.

Registering existing accounts does not create CRM users, wallets, products, or frontend relationships.

## Updating presentation fields

Send only fields that should change to `PATCH /api/v1/master/{master_id}`. Supported integration fields are `name`, `strategy_name`, `strategy`, `min_deposit`, and `default_perf_fee`. A new minimum affects future assignment validation; it does not move existing funds.

Changing a Master's default does not update existing Investors. Their effective rate must be read or changed through the [Investor performance fee endpoints](https://pamm-api.exuratech.com/reference/performance-fees.md).

> [!WARNING]
>
> Do not credit a Master account through an external MT5 deposit. Only PAMM-generated movements should alter its pool balance.

> [card] [Previous: End-to-end workflow](https://pamm-api.exuratech.com/guides/end-to-end.md)
>
> Return to the complete lifecycle.

> [card] [Next: Investors](https://pamm-api.exuratech.com/guides/investors.md)
>
> Provision the accounts that hold customer capital.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.