Deletions - MAM Docs

Master

Method	Path
`GET`	`/api/v1/mam/account-deletions/impact?master_login={login}`
`POST`	`/api/v1/mam/account-deletions`
`GET`	`/api/v1/mam/account-deletions/{operation_id}`
`POST`	`/api/v1/mam/account-deletions/{operation_id}/retry`

scope accepts MASTER_ACCOUNT_ONLY or MASTER_AND_INVESTORS. In the latter case, send only direct, eligible followers in investor_logins.

Investor

Method	Path
`GET`	`/api/v1/mam/investor-account-deletions/impact?investor_login={login}`
`POST`	`/api/v1/mam/investor-account-deletions`
`GET`	`/api/v1/mam/investor-account-deletions/{operation_id}`
`POST`	`/api/v1/mam/investor-account-deletions/{operation_id}/retry`

If an account also operates as a master, the impact response indicates that you must follow the master workflow. Deletion is blocked while the account participates in a cascade-fee charge with status PENDING, CLAIMED, or DEBITED. Use the cascade-fee charge endpoints to identify the pending obligation before retrying.

Transmitted-position policies

CLOSE_TRANSMITTED: requests closing before removing the relationship.
KEEP_OPEN: leaves positions in MT5 outside MAM tracking.

Deactivating or deleting the MT5 user belongs to the broker’s administrative process and is not performed by these endpoints.

Last modified on September 7, 2026