Skip to content
METARPC / DEVELOPER GUIDES

Trade copying.
Built with C++.

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 Windows with HTTP/2 support, Visual Studio C++ Build Tools and CMake 3.15+. Install dependencies and run the read-only List example. Keep your key in MRPC_API_KEY.

#include <copier/copier.hpp>
#include <cstdlib>
#include <iostream>
int main() {
    const char* key = std::getenv("MRPC_API_KEY");
    if (!key || !*key) { std::cerr << "Set MRPC_API_KEY\n"; return 1; }
    copier::CopierService service("copy.mrpc.pro:443", key);
    auto result = service.List();
    if (!result.ok) { std::cerr << result.error << "\n"; return 1; }
    for (const auto& item : result.copiers) std::cout << item.id << ": paused=" << item.paused << "\n";
}

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.