Trade Copier Docs

Rule Engine

Define many-to-many replication policies with symbol maps, risk multipliers, and per-target overrides.

Account Inventory

Attach source and destination MT4 or MT5 accounts once, then reuse them across rule sets.

Sync Analytics

Track copy latency, execution divergence, and worker health from a unified control plane.

Quick Start

Provision source and destination accounts, define the replication policy, then activate the rule set from the dashboard or API.

The control plane is intentionally split between rule management, operational monitoring, and delivery telemetry.

JSON

{
  "name": "Primary scalper -> funded accounts",
  "sourceAccount": "mt5-source-01",
  "targets": ["mt5-target-11", "mt5-target-12"],
  "riskMultiplier": 0.8,
  "symbolMap": {
    "GER40": "DE40"
  }
}

Rule Design

Rules support symbol mapping, slippage constraints, lot multipliers, inverse copying, and account-level safety overrides.

Model your rules declaratively so operational teams can inspect and approve changes quickly.

Source & Target Accounts

Attach MT4 and MT5 accounts, segment them into portfolios, and reuse account groups across copier configurations.

Monitoring & Analytics

Track copy latency, fill success, divergence, and per-rule throughput. Use these views to spot broker-specific execution issues before they impact clients.

Authentication & Headers

Copier services use the same workspace API key model as the main platform. Long-running sync workers should authenticate through environment-scoped keys.

When creating or updating a rule, persist the rule revision id returned by the API so rollouts and rollbacks stay deterministic.

Header	Value	Use	Description
Authorization	Bearer <api-key>	Required	Workspace credential used for copier control-plane access.
x-request-id	req_copy_1021	Recommended	Idempotency key for rule updates and account attachments.
x-workspace-id	core-prod	Optional	Explicit workspace selector for multi-workspace operators.
Content-Type	application/json	Write calls	JSON payload format for rules and account operations.

Endpoint Matrix

Rules

Method	Path	Purpose
POST	`/rules`	Create a copier rule set.
PATCH	`/rules/{id}`	Update risk, status, mapping, or rollout state.
GET	`/rules`	List active and paused rules.
POST	`/rules/{id}/replay`	Replay missed source events to targets.

Accounts

Method	Path	Purpose
POST	`/accounts/attach`	Attach a source or target account to the workspace.
GET	`/accounts`	Inspect account inventory and current health.
PATCH	`/accounts/{id}`	Change allocation, labels, or failover settings.
DELETE	`/accounts/{id}`	Detach an account from the copier fabric.

Analytics & Health

Method	Path	Purpose
GET	`/latency`	Return latency distribution and percentile data.
GET	`/fills/divergence`	Inspect fill mismatch and symbol mapping drift.
GET	`/health`	Read runtime health for worker pools and queues.
GET	`/events`	Stream rule state, sync, and worker events.

Errors & Limits

Rule updates should be treated as revisions. Persist the returned rule version and never assume an update becomes active until the rollout status confirms it.

Health and analytics endpoints are suitable for dashboards and alerting, while write-side rule changes should flow through approval or release gates.

Code	Name	Meaning
400	ValidationError	Rule definition or account attachment payload is malformed.
401	Unauthorized	Workspace token is missing or invalid.
409	RuleConflict	The requested rule revision conflicts with the current active version.
429	ReplicationBusy	The current workspace exceeded queue or replication capacity.
503	WorkerUnavailable	One or more copy workers are unavailable for assignment.

Deployment & Runtime

Copier deployments work best when rule orchestration, replication workers, and analytics jobs run as separate services with explicit queue boundaries.

For low-latency environments, pin source and target account workers close to their broker endpoints and alert on divergence instead of only raw latency.

Keep rule definitions under version control.
Monitor target lag, divergence, and worker retry count.
Use account labels to separate funded, demo, and internal pools.
Backfill analytics to a warehouse for longer-term quality tracking.