leader_login originates trades and follower_login receives them.
Before creating an allocation
- Both accounts are
ACTIVEand useHEDGING. - The leader has
can_be_leader=trueand an active profile. - The follower has
can_be_follower=true. - No live allocation exists for the same pair.
- The new relationship does not create a cycle.
- The follower meets
min_deposit.
POST /api/v1/mam/allocations/subscription-eligibility. This check does not create resources.
Allocation modes and mode_parameter
When sent,
mode_parameter must be greater than 0. A 0.5 multiplier halves the result, while 2 doubles it.
Leader limit
max_active_leaders_per_follower is the maximum number of active subscriptions a follower may have when subscribing to a master. For example, if max_active_leaders_per_follower=2, a follower with two or more active subscriptions cannot subscribe. When omitted, the system uses 3 by default.
Statuses
Retrieve changes incrementally
UseGET /api/v1/mam/allocations/events when your CRM needs to retrieve new allocations and status changes without downloading every allocation again.
id and send it as after_id in the next request. If has_more=true, continue immediately with next_cursor until the pending page is empty.
Common events are CREATED, UPDATED, and STATUS_CHANGED; payload_json retains a snapshot of the allocation associated with the change.
This feed supports reconciliation and recovery through polling. It does not replace the
mam.allocation.terminated webhook, which specifically reports a termination that has already been processed.Unsubscription
UsePOST /api/v1/mam/allocations/{allocation_id}/unsubscribe.
KEEP_OPEN: leaves positions open in MT5 but outside allocation management.CLOSE_ON_UNSUBSCRIBE: coordinates the closing of linked positions before completion.

