Skip to content
METARPC / DEVELOPER GUIDES

Trade copying.
Built with cURL.

From your first authenticated request to a monitored master–follower workflow. Clear examples, explicit sizing and practical recovery.

Start building → Explore the API
TLS transport · Owner authentication · Demo-first validation

  • 01 · Connect with confidence

    Understand keys, account IDs and transport before sending a request.

    Authentication →

  • 02 · Control the lifecycle

    Start once, inspect state, pause and clean up your test.

    Copier lifecycle →

  • 03 · Make sizing explicit

    Choose lot, balance or equity sizing and account for broker constraints.

    Sizing and settings →

  • 04 · Diagnose the result

    Separate network success from management success and broker execution.

    Troubleshooting →

Your first successful request

Requires cURL 7.76+ and Bash, or PowerShell 5.1+. Install dependencies and run the read-only List example. Keep your key in MRPC_API_KEY.

#!/usr/bin/env bash
set -euo pipefail
: "${MRPC_API_KEY:?Set MRPC_API_KEY to your real MetaRPC owner API key}"
case "${MRPC_API_KEY}" in
  [Tt][Rr][Ii][Aa][Ll]) echo "TRIAL is not a copier owner key" >&2; exit 1 ;;
esac
# Read-only. No accounts are created and no trades are placed.
curl --fail-with-body --silent --show-error --max-time 30 \
  -H "ApiKey: ${MRPC_API_KEY}" \
  --get --data-urlencode "userKey=${MRPC_API_KEY}" \
  "https://copy.mrpc.pro/UserCopiers"

Full setup · Testing guide · All SDKs

Watch a real demo failure and recovery

Copier troubleshooting video follows an oversized follower request from its broker rejection through a corrected demo opening and closing. It demonstrates the control-panel workflow; the lifecycle recipes, sizing guide and error guide explain how to apply the checks in this SDK.

Use disposable demo accounts first. Hosted service usage is paid; consult current pricing. A successful management response does not prove that a broker executed the copied trade.